On Mar 15, 9:14 am, Mark Murphy <mmur...@commonsware.com> wrote: > snctln wrote: > > So is it safe to say that on 1.5 systems GC from other processes > > affects performance for all processes? I know this graph is 3 months > > oldhttp://android-developers.blogspot.com/2009/12/knowing-is-half-battle... > > but phones are still being released with 1.5 (the motorola backflip > > was just released here in the states last weekend with 1.5 on it). > > I suspect so. If you go back in time (insert swirling imagery here) to > last year's tirades about Android and real-time games, foreign process > GC was the leading culprit, and there was solid evidence for it. That's > why they attempted to fix matters in 1.6, and, AFAICT, they succeeded. > And, based on the posts, game developers rejoiced in the new-found > smoothness. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android App Developer Training:http://commonsware.com/training
Ahhh, that makes sense. I might have been part of that tirade of real time game developers a year ago but around the time 1.6 was released my Android development took a back seat to my day job (c++ gui stuff) so I haven't really been caught up. I can say that the "lag" problem is less obvious on my Nexus 1 than on my ADP1, I just assumed it was due to the faster processor. I will try to put together some code this week that just draws some basic shapes moving around a SurfaceView to see if a simple test case has these problems as well. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
