On Tue, May 31, 2011 at 3:04 PM, bob <b...@coolgroups.com> wrote: > Does anyone know what the Android emulator bottleneck is on most PCs?
The bottleneck is in the emulator trying to do the graphics that it normally does with hardware acceleration. As Xav pointed out in the "Android Development Tools" Google I|O 2011 presentation, if you create a Honeycomb emulator with QVGA screen size (not realistic for production), it runs quickly. > Is it probably just the CPU? Insofar as a faster CPU will help a bit with faster CPU-based graphics work, yes. The real long-term answer is to get the UI to be rendered outside of the qemu emulation environment, using the actual hardware acceleration of your development machine. Watch the aforementioned presentation on YouTube for a demo. > Does anyone know of a computer where the > emulator works at a decent speed? 2.2 on down work fine for me on a dual-core 2.5GHz notebook. 2.3 is a bit sluggish. 3.x is painful even on a quad-core (not i7) 2.66GHz desktop. An i7 with Turbo Boost may help, simply because the emulator is single-threaded, so if you're not doing much else when the emulator runs, you can get 3.4GHz or thereabouts, depending on CPU. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in Oslo: http://bit.ly/fjBo24 -- 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