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

Using the SparseVhd option causes High CPU, RAM, and Disk usage #10991

Open
1 of 2 tasks
marsfan opened this issue Jan 7, 2024 · 5 comments
Open
1 of 2 tasks

Using the SparseVhd option causes High CPU, RAM, and Disk usage #10991

marsfan opened this issue Jan 7, 2024 · 5 comments

Comments

@marsfan
Copy link

marsfan commented Jan 7, 2024

Windows Version

Microsoft Windows [Version 10.0.22621.2861]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.133.1-microsoft-standard-WSL2

Distro Version

No response

Other Software

Docker Desktop v4.26.0

Repro Steps

  1. Add the following to .wslconfig
[experimental]
sparseVhd=true
  1. Enable sparse VHD for all existing distros with wsl --manage {DISTRO} --set-sparse true
  2. Attempt to create a large Docker container. (I'm using the make lint command from this project: https://github.com/marsfan/esp32_envionment_monitor/)

Expected Behavior

System CPU, RAM, and Disk Activity is not all running at 100%

Actual Behavior

During the process of creating the Docker container, my CPU usage is at 100%, as is my RAM usage, and my Disk usage on a SSD.

Furthermore, after the creation of the container, they all remain at 100% for a while, and the Modified part of the memory composition shown in task manager is a significant portion of my total RAM (I had it reach up to 10GB out of 16GB).

This only happens if I have sparse containers enabled. I have no knowledge of how WSL or sparse VHD files work, but I'm guessing its queuing up the changes to the VHD files in RAM, and then it takes a while to write everything to disk.

Diagnostic Logs

No response

@OneBlue OneBlue assigned ghost Jan 9, 2024
@DylanMerigaud
Copy link

You saved my ass, disabled the option for now, THANKS !

@mdstephenserdc
Copy link

also happened to me, thanks for this

@yangyang233333
Copy link

same

@MatMercer
Copy link

You saved my ass, disabled the option for now, THANKS !

And I didn't even enabled it to begin with, after researching for possible existing bugs lol.

@marsfan
Copy link
Author

marsfan commented Aug 10, 2024

@OneBlue You assigned this to someone back in January, but it seems that account was deleted. Is there anyone else you could assign this to in order to look into it?

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

No branches or pull requests

5 participants