我一直在使用英特尔(86)CPU/ABI。我用ARM(armeabi-v7a)创建了另一个模拟器，我发现速度有了很大的提高。我使用的是平台4.1.2 API级别16

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.

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

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

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

我一直在使用英特尔(86)CPU/ABI。我用ARM(armeabi-v7a)创建了另一个模拟器，我发现速度有了很大的提高。我使用的是平台4.1.2 API级别16

启用GPU硬件加速(除了Intel的HAXM)，如果你使用API 15 v3或更新版本和SDK Tools v17+。模拟器的图形加速利用开发计算机的图形硬件，特别是图形处理单元(GPU)，使屏幕绘制速度更快。这大大提高了速度。

要在模拟器上启用默认启用的图形加速:在创建AVD时，在“硬件”部分单击“新建”，选择“GPU仿真”并将值设置为“是”。

要只在运行时启用加速:在启动模拟器时使用-gpu标志，如下所示:

emulator -avd <avd_name> -gpu on

来源:谷歌的使用模拟器教程。