Ran some tests, overally, the emulator does show promise, but it still I don't see anything wrong in posting Leapdroid related information here.ĪFAIK, this emulator does use some Android-x86 code but it isn't fully

> (Note for clarification, I am not a list admin, just a standard subscriber.) > By all means let us know where we can subscribe to such a list. > your own set up which people can subscribe to if they wish? > have further updates sent here - I assume you have an announcements list of > not contributing code from Leapdroid to Android-x86, I think we don't need to > about it, but as it's not based on Android-x86 and (as far as I know) you're > Thank you for announcing your project to us, and letting us know some details

> more on a Leapdroid mailing list rather than on this one for Android-x86? > All very interesting, but may I propose that this sort of information belongs > We have done many things to make Leapdroid to be the fastest emulator. > On Thursday 30 June 2016 at 16:30:14, Huihong Luo wrote: Hopefully you can get some ideas now on why Leapdroid is faster compared to others, this is just one of the many reasons. We never use 32-bit viewer on 64-bit machines. We use 64-bit on 64-bit machines, and 32-bit on 32-bit machines. Within Leapdroid, the viewer and the headless vm launcher are inside the same process, so there is no inter-process communications, and thus the fastest performance. This fact alone reduces performances significantly. You can immediately see the downside on this architecture, as there are huge amount of inter-process data transfer. The VBoxHeadless.exe is the vm process, which handles huge amount of opengl data, and sends all these data to the 32-bit viewer process. Their viewer process is always 32-bit, even on 64-bit systems. Our competitors launch at least 2 processes for each vm, one process is VBoxHeadless.exe (64-bit or 32-bit, depending on the cpu), plus a 32-bit viewer process.

In other words, for each vm, our competitor uses one more process than us, which wastes cpu and memory, the worst is that it slows down performance. To launch n VMs, we will have to run n+1 processes (one process for each vm, then sharing one common LeapdroidSVC process), whereas all other emulators must run 2 * n + 1 processes. Leapdroid uses the least number of processes. We have done many things to make Leapdroid to be the fastest emulator.

Leapdroid for 1 gb ram