many are saying that windows defender real-time protection is the cause of the slow down. disable and try again.

This. Disabling Windows Defender through the group policy editor had a dramatic impact on speeding up file IO times in WSL. Granted, it's still much slower than native, but far better than before.

Lightworks "will cost you" money, as any Adobe product, so what are you comparing/complain there?

And BTW the Blender's video editor is very good, so yes theres is no good alternatives but don't underestimate Video editing Blender's capabilities because of that, i use it a lot with no complains.

Blender's handles perfect VBR videos/audio sync, Premiere doesn't, thats why i use it.

Great read. Good advice.

I'm also have some luck with Docker as opposed to full VM. It requires a bit of a different mindset but can be a great way to codify your setup. I'm running separate services for NeoVim, Rails, PostgreSQL, Redis, Webpack-dev-server and others. You can also make it more closely match your deployment env.

try vmware instead of virtualbox, years ago I had to do something similar, vmware had the best performance by far.

I did. Performance gains were negligible. For my use case, both had similar performance. Most of the time it's I/O dependent (source code editing, loading). Maybe in a situation where CPU-bound processes are more important, Vmware would win with a wider distance. But overall, they are pretty similar.

I'd be interested to see your same example run under Virtualbox with the virt-io drivers: https://www.linux-kvm.org/p...

In my experience, these drivers nearly halved my io-bound build times.

Those are drivers for Windows guest. The situation the author described is running Linux guest, so those drivers are useless.

That said, if you create a Linux VM under the latest VirtualBox, VBox will run the VM using "KVM virtualization". Switch the default network card from "Intel" to "Paravirtualized", and the Linux VM will run at very high speed as it offloads many processing to the host via the VBox KVM interfaces.

You're absolutely right; my mistake. I had used the virt-io drivers when running Windows from an OS X host.

Thanks for the information about KVM!

I've got a dumb question: why not hyper-v instead of virtualbox? Hyper-V on windows 10 has been pretty great for running Linux guests and is built in.

Not dumb, I tried it myself. But Hyper-V is good for headless machines. I want a full resolution, fast graphics pipeline. Hyper-V does not have good graphics support, so it fallback to slow (possibly) VESA. I can't have high resolutions nor fast renderings, (maybe if you're using Windows as a guest), but Linux with any GUI will be poor.

I just completed my setup and I agree. WSL is painfully slow. It is unusable for any real development task, I'm experiencing 300% speed increases on a VMWare.

Also, I still experience glitches and problems with most things that I do. Being either a PATH problem, some service that does not start, some weird error when running my tests, etc. It has improved a LOT from the original release but it is still far away from what a developer would need. Right now, WSL makes the tools something that you have to manage, aside from your code.

That is too bad :(

No Docker for Windows performance comparison?

Eu utilizo um MacBook Pro e uma outra Maquina com Ubuntu.

Now I'm using a dual-boot setup with Linux and Windows, however, in most part of the time I'm not using my home desktop to code. Since you provide this kind of test and show us that VirtualBox is good enough I will start to migrate now for this approach.
As usually are your posts, this is another excellent.