The Honeycomb emulator is faster on my dev system than the preview was, but it is highly sensitive to the emulated hardware. I am using 1024 megabytes of emulated RAM and a 256 meg vm heap size and I still see out of memory errors when the launcher tries to load wallpaper.
The AVD refuses to go above 1.5G or so of emulated RAM. I can't comment on Eclipse pegging the CPU, it is about the same as before. On Wed, Feb 23, 2011 at 6:54 AM, Reuben Scratton <reuben.scrat...@gmail.com> wrote: > I suspect Honeycomb emulator's performance is being crippled by every last > pixel now having to go through a pure software OpenGL pipeline. That will > have far more stages than the old 2D renderer had. > If you ever ran an OpenGL ES app on older emulators, you'd see similar > slowness... there is far more computation involved per pixel. > As for building and deploying, I am having a lot of trouble with the new > tools too... Win32 Eclipse Galileo here. Still investigating. > > -- > 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 -- 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
