high cpu/mem usage = debug version?
Posted: Sat Dec 22, 2007 11:04 am
i've been using/testing MM3 since the first RC and i gotta say i haven't been experiencing any problems at all and device sync seems a lot smoother too so im pretty happy
one thing that bothers me though is the relatively high cpu and mem usage in comparison to 2.x
i was wondering if this is something temporary and that once a 'final' build is made the code will get optimized a bit or if 3.0 is really that much heavier than 2.x
thanks!
one thing that bothers me though is the relatively high cpu and mem usage in comparison to 2.x
i was wondering if this is something temporary and that once a 'final' build is made the code will get optimized a bit or if 3.0 is really that much heavier than 2.x
thanks!
