> Is this a common trend? I find the emulator to be pretty slow in comparison to my NexusOne sitting right next to my PC. The factor is probably around 0.5x - 0.75x the speed. The PC is a Core2Duo 5400 3Ghz so no slouch by any means. I suppose that if they bothered to accelerate the GFX / etc.. and better utilize the virtualization functions they could squeeze out some more into the emulator. That said, having the emulator slower than most devices is a good (though incidental) test of how your app will run in the real world.
I don't know if its related, but in the last tooling update the debugger is killing my processing performance, like horribly. Try running the app stand-alone vs. debugging and make sure it isn't just debugging/profiling cutting into emulator performance. > And regarding memory - I am loading Eclipse with close to 1G to be > able to > run the emulator and its basic services - is that normal? The emulator runs in its own process. If you mean to actually get your app to launch then well Eclipse is a ram heavy platform. You get a ton of features for that investment. If you really need a slimmer eclipse, try to find features you don't use and remove them. Personally I peg my eclipse at heap 1.5g and permgen 256 and it never blinks (Even with the J2EE tools which eats resources like crazy). -- 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
