3 ms·

If you cross the IO boundary to the Windows FS, yes, it is slow and your compilation will be slow. You need to have the project in the WSL FS, it's always been

by meibo 4y ago

If you cross the IO boundary to the Windows FS, yes, it is slow and your compilation will be slow. You need to have the project in the WSL FS, it's always been this way and I get pretty much native performance this way. Your editor can navigate to the WSL filesystem instead.

csdvrx 4y ago
> If you cross the IO boundary to the Windows FS, yes, it is slow and your compilation will be slow If you need good IO performance, WSL1 is still a valid option. I need good IO performance, and it's not clear how much of the overhead is due to NTFS, and how much is due to 9p (to pass the VHDX file on the NTFS partition to WSL2) So I'm planning some experiments with OpenZFS for windows and NTFS3 (https://old.reddit.com/r/zfs/comments/10lcnpk/zfs_raw_passthrough_on_wsl_what_do_you_think_of/ https://old.reddit.com/r/zfs/comments/10lcnpk/zfs_raw_passth...), first using a WSL2 kernel with the option enabled (https://github.com/microsoft/WSL/issues/8564 https://github.com/microsoft/WSL/issues/8564 and https://github.com/bioluks/WSL2-Linux-Kernel-NTFS https://github.com/bioluks/WSL2-Linux-Kernel-NTFS) then WSL1. I have a dual NVMe setup and W11 for Workstations, so it should be possible to run a passthrough of both partitions to the kernel. However, it's not clear yet how to do that with a VHD on VHDX: most of the documentation I've read about VHD (or VHDX) refers to a passthrough as an "old" option: https://www.altaro.com/hyper-v/hyper-v-pass-through-disks/ https://www.altaro.com/hyper-v/hyper-v-pass-through-disks/
- 2fast4you 4y ago
  Have you considered swapping Windows and Linux? Depending on your use case, you can still get pretty good performance out of virtualized Windows if you use PCI-E passthrough
  - csdvrx 4y ago
    I have: I generally prefer Windows, but depending on the test results, this option is definitely on the table! As the computer has 2x NVMe and 2x GPU, it should be easy to do a GPU passthrough (with one GPU for Linux native, the other in passthough to Windows) but this brings a little extra complexity I'd rather avoid if I can.

by meibo 4y ago

csdvrx 4y ago

> If you cross the IO boundary to the Windows FS, yes, it is slow and your compilation will be slow If you need good IO performance, WSL1 is still a valid option. I need good IO performance, and it's not clear how much of the overhead is due to NTFS, and how much is due to 9p (to pass the VHDX file on the NTFS partition to WSL2) So I'm planning some experiments with OpenZFS for windows and NTFS3 (https://old.reddit.com/r/zfs/comments/10lcnpk/zfs_raw_passthrough_on_wsl_what_do_you_think_of/ https://old.reddit.com/r/zfs/comments/10lcnpk/zfs_raw_passth...), first using a WSL2 kernel with the option enabled (https://github.com/microsoft/WSL/issues/8564 https://github.com/microsoft/WSL/issues/8564 and https://github.com/bioluks/WSL2-Linux-Kernel-NTFS https://github.com/bioluks/WSL2-Linux-Kernel-NTFS) then WSL1. I have a dual NVMe setup and W11 for Workstations, so it should be possible to run a passthrough of both partitions to the kernel. However, it's not clear yet how to do that with a VHD on VHDX: most of the documentation I've read about VHD (or VHDX) refers to a passthrough as an "old" option: https://www.altaro.com/hyper-v/hyper-v-pass-through-disks/ https://www.altaro.com/hyper-v/hyper-v-pass-through-disks/

2fast4you 4y ago
Have you considered swapping Windows and Linux? Depending on your use case, you can still get pretty good performance out of virtualized Windows if you use PCI-E passthrough
- csdvrx 4y ago
  I have: I generally prefer Windows, but depending on the test results, this option is definitely on the table! As the computer has 2x NVMe and 2x GPU, it should be easy to do a GPU passthrough (with one GPU for Linux native, the other in passthough to Windows) but this brings a little extra complexity I'd rather avoid if I can.