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.

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

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

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

更新:现在Intel x86映像已经可用，最好的答案是上面的zest。

正如CommonsWare正确指出的那样，这个模拟器很慢，因为它模拟的是ARM CPU，而ARM CPU需要转换成Intel操作码。这种虚拟化占用CPU资源。

为了让模拟器更快，你必须给它更多的CPU。从快速CPU开始，如果可以的话升级。

然后，给模拟器更多的CPU:

Disable Hyperthreading - Since the emulator doesn't appear to utilize more than one core, hyperthreading actually reduces the amount of overall CPU time the emulator will get. Disabling HT will slow down apps that take advantage of multiple CPUs. Hyperthreading must be disabled in your BIOS. Make the emulator run on a CPU other than CPU 0 - This has a much smaller impact than turning off HT, but it helps some. On Windows, you can specify which CPU a process will run on. Many apps will chew up CPU 0, and by default the emulator runs on CPU 0. I change the emulator to run on the last one. Note that on OS X you cannot set affinity (see: https://superuser.com/questions/149312/how-to-set-processor-affinity-on-a-mac).

我看到在这两个改变到位后，大约有50%的改善。

在Windows 7上设置处理器亲和性:

打开任务管理器 单击“查看所有进程”(以管理员身份运行，否则无法设置处理器相关性) 右键单击模拟器.exe并选择设置亲缘性… 在Set Affinity对话框中，只选择最后一个CPU

注意:当您以这种方式更改关联时，它只在流程的生命周期内更改。下一次开始，你必须再来一次。

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

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