> The ~100-300ms isn't that meaningful of a figure, though. Frame rate > won't drop because of elapsed time of the foreign process' GC operation. > Frame rate will drop if, during that time, too much CPU is utilized by > GC, or access to some cross-process resource is blocked by GC, or > something along those lines. Lacking any of that, it doesn't matter if a > foreign process' GC takes 100ms or 100 minutes.
I won't claim to know the ins and outs of the Dalvik GC, but I wouldn't be so quick to assume that the GC from a foreign process will just take its sweet time in a low priority thread in such a way that won't impact frame-rate. There are many factors involved (some you have pointed out) and it'd be great to get some detailed information from the devs on how the GC behaves under these circumstances. To answer your question, the frame rate drops i'm seeing are severe (game usually runs at > 30 fps, but dips down to 5-10 fps when a spike occurs). You bring up some interesting test cases. I'll be happy to play around with some of these scenarios when I have time.. as well as log a bug when I collect enough evidence. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
