Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Direct Use of Physical Partition as WSL System Disk for Improved Performance #12244

Open
Ocyss opened this issue Nov 6, 2024 · 4 comments
Open
Labels

Comments

@Ocyss
Copy link

Ocyss commented Nov 6, 2024

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.

Image

@Ocyss Ocyss added the feature label Nov 6, 2024
@Ocyss Ocyss changed the title [feat] Direct Use of Physical Partition as WSL System Disk for Improved Performance Direct Use of Physical Partition as WSL System Disk for Improved Performance Nov 6, 2024
Copy link

github-actions bot commented Nov 6, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Copy link

github-actions bot commented Nov 6, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@Ocyss
Copy link
Author

Ocyss commented Nov 6, 2024

Logs are required for review from WSL team

WSL 团队需要审核日志
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.如果这是一个功能请求,请回复“/feature”。如果这是一个问题,请用“/question”回复。 Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.否则,请按照以下说明附加日志​​,除非添加日志,否则您的问题将不会被审核。这些日志将帮助我们了解您的机器中发生的情况。

How to collect WSL logs
如何收集WSL日志

View similar issues 查看类似问题

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!请查看下面的问题,看看它们是否能解决您的问题,如果该问题描述了您的问题,请考虑关闭此问题并点赞另一个问题,以帮助我们优先处理它!

Open similar issues: 打开类似问题:

Closed similar issues: 已关闭类似问题:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.注意:您可以通过赞成或反对此评论来向我提供反馈。

/feature

Copy link

github-actions bot commented Nov 6, 2024

Diagnostic information
Found '/feature', adding tag 'feature'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant