What can you expect out of an ARM emulator running on an x86 machine? Every instruction had to be converted from ARM to x86 architecture which makes it really slow. But they were too slow to use, the reason being a change of architecture. Long ago Android emulator was the only way to go. Psst: I have some benchmarks down the line, stick around. But it is slower when running tests compared to certain Android emulators.Ī little background on the subject and then we’ll jump to the good stuff. They have other products like Genymotion on Cloud & Genymotion on Demand which are not being considered here. Wherever I say Genymotion I mean Genymotion Desktop. running tests.Īll benchmarks were done on a mid-2015 MacBook Pro. Use x86 (32 bit) image with Google APIs, 3GB ram, quad-core CPU.ĭisclaimer: I’ve tested my use case which to me looks the general use case i.e. TL DR: Android emulator is faster than Genymotion when configured right. Based on this I’ll be evaluating all the android emulators along with Genymotion. I’ve gathered some data around the most common use case in my experience.

I’ve seen most of the discussion ending in favour of Genymotion. There has always been a debate about which android emulator to choose or to go with Genymotion.

Mac android studio emulator slow