On Jun 11, 1:41 pm, David Given <[EMAIL PROTECTED]> wrote: > IIRC, the current Dalvik VM is interpreted, not a JIT, which means that > performance is going to be abysmal. A better VM should raise the > performance by at least one order of magnitude, more like two. I think > that trying to benchmark m5 is probably not going to produce any results > representative of a final product.
The Dalvik interpreter is certainly good enough for the class of devices we are running on. Note that in almost all of the demos that have been shown, what you have seen is the Dalvik interpreter running on about the same class of hardware: 350MHz CPU, 128MB RAM. And it's not just the apps that are run by Dalvik, but almost the entire platform is run by it (including the activity manager, package manager, window manager, view hierarchy, etc). Also a key aspect of getting good performance on these devices is basic tuning. For example, depending on how your kernel is configured, you may end up with much less memory available to applications, start paging, and see your performance drop like a rock. Likewise in M5 we started making use of hardware graphics acceleration and tuning the UI around that feature, so if you don't have that hooked up you will see much worse performance in various areas. That said, the M5 release was a fair amount heavier than M3, largely because we were in the middle of some major reworking of core parts of the framework. The 1.0 release will be much closer to M3 in performance, and with things like hardware acceleration support will significantly outperform it in key areas. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
