使用Genymotion代替模拟器。Genymotion的性能更好 https://www.genymotion.com

更新当前的Android Studio到Android Studio 2.0，并更新系统映像。

Android Studio 2.0模拟器的运行速度比Android之前的模拟器快3倍，通过ADB的增强，您现在可以将应用程序和数据推送到模拟器，比推送到物理设备快10倍。与物理设备一样，官方Android模拟器也内置了谷歌播放服务，因此您可以测试更多的API功能。最后，新的模拟器具有丰富的新功能来管理呼叫、电池、网络、GPS等。

编辑虽然使用英特尔图像可以获得一些性能提升，但使用Genymotion获得的性能要大得多。请看保罗·拉默茨马的回答。

以前的回答

ADT rev 17模拟器支持在Windows和Mac OS x上以虚拟化模式运行x86系统映像，这对性能有显著影响。

ADT rev 17注释: http://android-developers.blogspot.jp/2012/03/updated-sdk-tools-and-adt-revision-17.html

配置虚拟机加速: http://developer.android.com/guide/developing/devices/emulator.html#accel-vm

Thank you @zest! Worked like a charm. Some things of note: Need to apply Intel's hotfix for the HAXM to deal with kernel panic issue: http://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager Also, note, if you have more than one abi, you need to uninstall one due to a bug in the latest version of the Android API (r19): https://code.google.com/p/android/issues/detail?id=66740 (remove armeabi-v7a in this case, since you want the x86 abi). Other than the 45-minutes it took me to resolve these, it was an very rewarding exercise in terms of the increased performance of the emulator.

I think it is because clr virtual machine uses cpu directly without code opcode translation. It may be optimization for clr application or may be windows mobile/window phone 7 started on INTEL proccessor. Android platform based on linux and theoretically you can start android on virtual machine in i686 environment. In this case virtual machines such as vmware could execute some opcodes direcly. But this option will be allowed only if you write on the Java. Because the Java interpret their byte-code or precompile it before execution. see: http://www.taranfx.com/how-to-run-google-android-in-virtualbox-vmware-on-netbooks

我最近从core 2 @ 2.5, 3gb内存换成了i7 @ 1.73, 8gb内存(两个系统都运行Ubuntu 10.10)，现在模拟器的运行速度至少快了一倍。投入更多硬件当然会有所帮助。