Parallelize workload pack downloads Fixes #43870 #45969
Draft
+61
−56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-issue-labeler
bot
added
Area-Workloads
untriaged
|
You may need to build a local copy that he can install and try. Now that sdk and installer are merged, you might be able to just run build -pack locally in your branch and create zips for private testing. |
|
Could also just drop-in replace dotnet.dll, no? Because this command is entirely part of the CLI, not touching anything in the SDK props/targets/etc. |
This was referenced Jan 15, 2025
Open
I'd be happy to. But yes, a binary would help as I haven't practiced building this repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #43870
There are multiple possible reasons AzDO might be much slower than nuget.org. My untested hypothesis is that it may be some authentication work, which would be substantially mitigated by parallelizing the workload pack downloads (not the installs). That's what I tried to do here.
@AArnott, any chance you could try this out and let me know if it helps?