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

Check if moving the .NET SDK install dir to the D drive on Windows makes the builds faster (OSOE-928) #402

Closed
Piedone opened this issue Dec 4, 2024 · 2 comments · Fixed by #403
Assignees

Comments

@Piedone
Copy link
Member

Piedone commented Dec 4, 2024

See actions/setup-dotnet#260 (comment).

Jira issue

@github-actions github-actions bot changed the title Check if moving the .NET SDK install dir to the D drive on Windows makes the builds faster Check if moving the .NET SDK install dir to the D drive on Windows makes the builds faster (OSOE-928) Dec 4, 2024
@Piedone
Copy link
Member Author

Piedone commented Dec 4, 2024

Results: Measurements.xlsx

The NuGetTest workflows got about 11% slower, but with a much larger standard deviation, so I'm not entirely sure how much to trust this (given that workflows get basically random VMs). But we need to use this hardware anyway.

The root workflows got 6% faster on average, but there the original runtime had a larger standard deviation.

I'm not confident that anything really changed here.

@Piedone
Copy link
Member Author

Piedone commented Dec 11, 2024

Also setting NUGET_PACKAGES to the D drive as suggested under actions/setup-dotnet#260 (comment) helped a lot:

OSOCE measurements.xlsx

This caused an about 14% reduction in total workflow runtime for the root solution, and 25% for the NuGetTest one.

The root solution build, compared to the larger 8-core runners, takes 18,5% more, but not 38,5% as before. I'm inclined to switch our builds over to that, since it's free.

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

Successfully merging a pull request may close this issue.

1 participant