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

Explore using a dev drive for windows CI #3508

Closed
konstin opened this issue May 10, 2024 · 2 comments · Fixed by #3522
Closed

Explore using a dev drive for windows CI #3508

konstin opened this issue May 10, 2024 · 2 comments · Fixed by #3522
Labels
internal A refactor or improvement that is not user-facing windows Specific to the Windows platform

Comments

@konstin
Copy link
Member

konstin commented May 10, 2024

We observe that windows is much slower on any io operations, e.g. just downloading and unpacking the python versions takes 1.5min. We should explore using using a VHDX virtual harddisk as described in actions/cache#752 (comment) to see if this solves the performance bottleneck in github actions.

@notatallshaw
Copy link
Contributor

notatallshaw commented May 10, 2024

FYI there are some details here where this was reccomended for pip to do: pypa/pip#12055

Ultimately pip maintainers are very conservative about adding new features, but you might find the post informative.

@charliermarsh charliermarsh added internal A refactor or improvement that is not user-facing windows Specific to the Windows platform labels May 10, 2024
@zanieb
Copy link
Member

zanieb commented May 11, 2024

See also, this brief GitHub Actions thread requesting this feature: actions/runner-images#8698

zanieb pushed a commit that referenced this issue May 13, 2024
## Summary

Switch to using Virtual HD + ReFS to speed up windows jobs.

Closes #3508
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal A refactor or improvement that is not user-facing windows Specific to the Windows platform
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants