I do believe the M1 designs are better suited for sustained loads, so with the new Apple stuff this problem should be gone. Similar problems also exist with cheap netbooks that just have insufficient cooling on the processor. This can make a system that normally feels snappy and fast run terrible slow with an emulator. There's also the addendum that many Apple products sporting an Intel CPU have had their power/performance curve and fan curves tweaked to be silent and super performant in short loads (compiling a single file, opening a browser, loading a page, etc.) but clocking down hard and long if you run a sustained load on them, especially with a multi core load.
Android with software rendering won't be a bit slower and choppier like you see in desktop VMs it will be absolutely unusable for anything but a cursory check to see if the software even runs at all. If that's unavailable on your platform (because, for example, your driver is considered buggy by the emulator devs (common on Linux with proprietary drivers) or if all you've got is an integrated Intel GPU that already has its hands full rendering to your 4k screen), your experience will be terrible with any Android emulator. One problem I've run into has been that Android relies heavily on GPU acceleration. With proper acceleration (which may be unavailable on Windows without some tweaking, even after installing HAXM!), Android will run similar to a standard Linux VM, at near native speeds. Performance through QEMU (ARM on 圆4, 圆4 on M1) is terrible, of course, but that's to be expected with software instruction translation. Performance is perfectly fine as long as you pick an image with your computer's native instruction set and have hardware acceleration.
0 kommentar(er)
