Direct Use of Physical Partition as WSL System Disk for Improved Performance
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
**Is your feature request related to a problem? Please describe.**
I'm experiencing severe performance issues while using WSL for full-stack development, with my disk usage frequently hitting 100%. I suspect this is related to storing the `ext4.vhdx` file on a developer disk formatted with ReFS.
**Describe the solution you'd like**
I would like to have the ability to use a physical partition as the system disk for WSL directly. I believe this change could potentially enhance performance and allow for simpler storage management.
**Describe alternatives you've considered**
While considering moving the `ext4.vhdx` to another partition, I thought of this potentially better solution, as dedicating a single partition just to store a VHDX file seems extremely inelegant to me.
**Additional context**
I will continue to track the issue of disk usage reaching 100% in a short time during development and provide feedback on my experience.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by locating the WSL storage and system-disk handling relevant to physical partitions. Done would mean a defined and supported way to use a physical partition directly as the WSL system disk, with appropriate validation and tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100