loadingarts.blogg.se

This is my performance in a medium project:

So maybe the performance is bottlenecked by this bug as well. It goes back down a while after quitting my shell. By the 3rd copy action all my RAM is used up (32GB). Īs another interesting fact, the vmmem usage while writing the file is increasing rapidly. WSL dd if=/dev/zero of= /testfile bs=1M count=10000ġ0485760000 bytes (10 GB, 9.8 GiB) copied, 7.0873 s, 1.5 dd if=/dev/zero of=/testfile bs=1M count=20000Ģ0971520000 bytes (21 GB, 20 GiB) copied, 51.3779 s, 408 dd if=/dev/zero of=~/testfile bs=1M count=20000ġ2960399360 bytes (13 GB, 12 GiB) copied, 12.1766 s, 1.1 GB/s dd if=/dev/zero of=~/testfile bs=1M count=10000ġ0485760000 bytes (10 GB, 9.8 GiB) copied, 29.7096 s, 353 thinking this has to do something with OS Caching because in task manager even though I can see the file being written, the disk usage write speed is unchanged while in wsl1 I can see it constantly at around 350mb/sec. I've repeated the write tests in both environments a few times now and there's no consistent result.

I'm assuming you're still refering to / and not /mnt folders about namespace operations.

I would expect the filesystem performance in /mnt to at least be on the same level but it's over 10 times slower.Īnother interesting fact is that if I mount the same drive as a cifs share I get 3x performance WSL 2 (cifs dd if=/dev/zero of=/mnt/sambae/testfile bs=1M count=10000ġ0485760000 bytes (10 GB, 9.8 GiB) copied, 84.001 s, 125 MB/s An update of the current status because it's way too hidden in this thread.

I decided to open this as a separate issue because although it's related to the generic issue of filesystem performance it's directly related to WSL 2 while the other issues are for WSL 1 and it's showing very conflicting results.