好吧，问题是从2011年开始的，我在2022年回答，根据我的经验，最好的答案是从命令启动模拟器，这样模拟器就会启动一个专用的进程，而不是android studio的子进程。如果进程是独立的，那么它将能够正确地使用GPU，并可以利用所有资源，不像从设备管理器启动模拟器。 你可以从设备管理器中创建AVD并从下面的AVD文件夹中独立启动模拟器。

如何打开模拟器命令行

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.

启用这个选项对我很有效。

AVD管理器->选择设备并单击“编辑”->启用“使用主机GPU”选项

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

好吧，问题是从2011年开始的，我在2022年回答，根据我的经验，最好的答案是从命令启动模拟器，这样模拟器就会启动一个专用的进程，而不是android studio的子进程。如果进程是独立的，那么它将能够正确地使用GPU，并可以利用所有资源，不像从设备管理器启动模拟器。 你可以从设备管理器中创建AVD并从下面的AVD文件夹中独立启动模拟器。

如何打开模拟器命令行