3 ms·
Its 1.2x not 35x. 282MiB used on the host to run the VM with 128MiB of available RAM inside so 154MiB overhead.
by vel0city 4y ago
Its 1.2x not 35x. 282MiB used on the host to run the VM with 128MiB of available RAM inside so 154MiB overhead.
- justsomehnguy 4y agoAvailable != used. Actual total usage could be bigger if all memomry in the VM would be consumed.
- jchw 4y agoI am pretty sure v86 allocates all of the memory ahead of time, using one big array buffer. It’d probably be easy to find the code. However, that doesn’t mean that Chrome is actually allocating it all at once. It could very well be paging it in on demand. I have no idea. In that case, to measure the overhead, you’d need to fill the guest memory. I didn’t bother looking into it that deeply because I don’t really think it’s that interesting; an Electron x86 emulator is pretty impractical no matter how you shake it. It’s still pretty funny, though.