On Jun 12, 8:22 am, David Given <[EMAIL PROTECTED]> wrote: > I haven't seen any devices personally, but some of the people where I > work saw some at MWC and their reaction was uniformly that it was > unacceptably slow. I don't know what hardware or codebase that was, of > course.
Without knowing anything about the hardware or software running on them, I would be very hesitant to make many assumptions from that. > Certainly, the emulator's slow to the point of being only marginly > usable on my home machine --- 3.2GHz Celeron D --- and sluggish but > better on my work machine --- a 2.4GHz Core Duo. The emulator's speed > isn't representative of very much, of course. No, it isn't -- it is running an ARM emulator of the entire software stack, including the kernel. Plus no graphics hardware acceleration, etc. > Sure, but there are other key areas that are pure number-crunching --- > there are a lot of complaints on the -developers list right now that > view inflation is really slow, for example, and that hits performance > right where the user will notice it: application startup. View inflation is not number crunching. And these are all from people running the emulator, on who knows what desktop PC, so you just can't take that experience and make many correlations to actually running on a device. That said, you certainly don't want to have a UI with 100s of views, because it will be slow. But this is as much because you are trying to run on a mobile device and not a desktop computer -- in general mobile CPUs are much slower than their actual MHz may make you think. > Given that > JITs these days are known technology, not particularly hard to do, and > give such staggering performance improvements I'd be really surprised if > one wasn't on the roadmap *somewhere*, and I'd expect it to be sooner > rather than later. It is not that simple. There are both advantages and disadvantages to using a JIT. One of the disadvantages is more memory use, and memory use is actually about our #1 performance issue on actual hardware. Using more memory means fewer applications processes you can have ready to run, less data you can cache from disk, more times you need to page code off of disk, etc. At any rate, there definitely won't be a JIT in 1.0, it's just not that necessary. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" 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-internals?hl=en -~----------~----~----~----~------~----~------~--~---
