I’m super excited about this. Particularly dev drive, which will hopefully speed up my workflow. It’s amazing how slow the C drive is. Partly that’s for legacy reasons (e.g. 8.3 names, filesystem filters, etc). Partly that’s the AV (seriously slow). Most of these things can be addressed by manually making a new drive, tweaking it with fsutil, excluding folders in the AV, etc. But I’d love to be able to avoid the hassle and get some extra perf on top.
One thing that I’m curious about: right now, the thing that tanks perf when developing on Windows is Windows Defender. That’s trivial (if annoying) to disable for certain areas (say, ~\Source or something), which helps a ton, but NTFS’ back compat in terms of data structures then ends up dominating. I kind of ignored ReFS when it was announced, since it seemed very incomplete and practically DOA, so I’m not actually sure how it’ll do here, but I’m really optimistic (especially given its CoW semantics when you’re using Git) that it’ll be just a ridiculous speed improvement across the board.
I’m surprised OSes haven’t done more in general to court the developer workflow. I used to use Fedora workstation and couldn’t tell any differences from any other linux configs I tried. So far this looks like just an all-in-one github place, but I’m hopeful to see where it goes.
I don’t use Windows, but my Colleagues do, and I think the “Dev Drive” is the big feature here that hopefully people use. From what I heard, WSL and the NTFS filesystem are brutal to use big code bases with. Hopefully this solves some of those problems.
I may be wrong but I don’t think this will help with WSL. If you access the Windows host filesystem then it goes through a 9P fileserver, which is slow. For best performance, files should be stored or transferred to a filesystem within WSL so they can be worked on without the overhead.
I’m super excited about this. Particularly dev drive, which will hopefully speed up my workflow. It’s amazing how slow the C drive is. Partly that’s for legacy reasons (e.g. 8.3 names, filesystem filters, etc). Partly that’s the AV (seriously slow). Most of these things can be addressed by manually making a new drive, tweaking it with fsutil, excluding folders in the AV, etc. But I’d love to be able to avoid the hassle and get some extra perf on top.
One thing that I’m curious about: right now, the thing that tanks perf when developing on Windows is Windows Defender. That’s trivial (if annoying) to disable for certain areas (say,
~\Sourceor something), which helps a ton, but NTFS’ back compat in terms of data structures then ends up dominating. I kind of ignored ReFS when it was announced, since it seemed very incomplete and practically DOA, so I’m not actually sure how it’ll do here, but I’m really optimistic (especially given its CoW semantics when you’re using Git) that it’ll be just a ridiculous speed improvement across the board.I’m surprised OSes haven’t done more in general to court the developer workflow. I used to use Fedora workstation and couldn’t tell any differences from any other linux configs I tried. So far this looks like just an all-in-one github place, but I’m hopeful to see where it goes.
I don’t use Windows, but my Colleagues do, and I think the “Dev Drive” is the big feature here that hopefully people use. From what I heard, WSL and the NTFS filesystem are brutal to use big code bases with. Hopefully this solves some of those problems.
I may be wrong but I don’t think this will help with WSL. If you access the Windows host filesystem then it goes through a 9P fileserver, which is slow. For best performance, files should be stored or transferred to a filesystem within WSL so they can be worked on without the overhead.
Ah, then I misunderstood the point of the “Dev Drive” all together it seems.