The Android Emulator uses virtualization to emulate the device at all. One of two virtualization engines can be used within the Windows operating system – HAXM a HyperV.
In case of AMD / Ryzen processors it is necessary to use HyperV technology (HAXM does not work on AMD processors), in case of Intel processors HAXM or HyperV can be used.
Since I have an Intel CPU in my CPU (namely, the slow CPU – Intel G4560), I made a comparison of the speed of the HAXM and HyperV engines.
With normal boot / boot under HAXM, the emulated device starts in about 14.46 seconds.
In normal boot under HyperV, the emulated device will start in about 32.04 seconds.
For comparison, a normal boot on both engines.
It can be seen that using the HAXM engine will boot the device in less than half the time.
More interesting is the quick / quick boot. A quick boot is used on Android Emulator every time you exit the Android Emulator, but does not directly shut down the device.
In the case of quick boot, the two engines are more or less equally fast.
With Quick Boot under HAXM, the emulated device will start in about 1.96 seconds.
In Quick Boot under HyperV, the emulated device runs in about 1.95 seconds.
For comparison, quick boot on both engines.
You can see that the quick boot on both engines is just as fast.
Conclusion
With normal boot times, HAXM is twice as fast as HyperV. But with quick boot, both engines are already as fast.
| Engine | Boot | Čas |
|---|---|---|
|
HAXM |
Normal |
14,46 |
|
HyperV |
Normal |
32,04 |
|
HAXM |
Quick |
1,96 |
|
HyperV |
Quick |
1,95 |
Pingback: Flutter for Tizen: The Basics – Mullr Dev