I compared memoryusage and performance of Google Androidand Microsoft Emulators. Here are some numbers:
Android Emulator x86 system image - Memory allocated: 1.06GB
Android Emulator ARM system image - Memory allocated: 1.10GB
Microsoft Emulator for Pocket PC ARM - Memory allocated: 0.21GB ( 213MB )
Microsoft Emulator for Smartphone ARM - Memory allocated: 0.21GB ( 213MB )
Microsoft Emulator for Windows Mobile ARM - Memory allocated: 0.34GB ( 339MB )
Take into account that three (!) Microsoft Emulators for different platformsused less (!)memory:
( 0.21GB + 0.21GB + 0.34GB = 0.76GB ) < ( 1.06GB or 1.10GB )
then one Android Emulator.
Microsoft Emulators are significantly faster (!) than GoogleAndroid Emulator.
What is wrong with GoogleAndroid Emulator?
I think there are design and implementationissues and Google Software Developers over complicated
internals of the Android Emulator. Android Emulator system images are ~10x bigger than Microsoft system
images for ARM CPUs
Does it mean that Android OS and Emulator codes are less optimized, or not optimized at all?
If Google Software Developers don'toptimize codesit ispossible that in a couple of years Android OS,
designed for Mobile Devices in the first place, will be compared in size with Windows XP or even Windows 7
operating systems for Desktop computers and will have more performance problems.
Google admitted that there are performance problems with Android Emulator however an attempt to fix
these problems with GPUs is not a right solution and the source codes should be optimized and all "junk codes" deleted.
Here three screenshots of Windows Task Manager: