Skip to content

Workspace restore runs stale projects concurrently (bounded) (#563) - #618

Merged
MelbourneDeveloper merged 3 commits into
mainfrom
chore/finish-plans-7
Nov 20, 2026
Merged

MelbourneDeveloper merged 3 commits into
mainfrom
chore/finish-plans-7

Conversation

@MelbourneDeveloper

Copy link
Copy Markdown
Collaborator

Implements the PERFORMANCE-PLAN [PERF-PROGRESSIVE-LOAD] item "restore projects concurrently (bounded)".

  • WorkspaceRestore restores stale projects with Parallel.ForEachAsync, at most 2–4 SDK restores at a time (each restore is its own MSBuild process).
  • The first failure is still the one reported, in project order, but it no longer stops the projects after it from restoring.
  • WorkspaceRestoreConcurrencyTests uses real projects whose restore deliberately takes 6s. Two of them must finish in less than the 12s they take one after the other; both are restored exactly once, and a second open restores nothing. A failing project in the middle is the one named in the error, with NU1101, and the project after it is still restored.

Both tests failed before the change: the projects ran in series (14.7s for three 4s restores), and the project after the failure was abandoned.

…K restores, reporting the first failure in project order without abandoning the rest (#563)
@MelbourneDeveloper
MelbourneDeveloper enabled auto-merge (squash) November 20, 2026 04:41
…d windows, not wall-clock time a loaded runner can stretch
…ng: a heap read before the loop starts has no Widgets, which a loaded runner exposed
@MelbourneDeveloper
MelbourneDeveloper merged commit 8d43eb5 into main Nov 20, 2026
117 of 119 checks passed
@MelbourneDeveloper
MelbourneDeveloper deleted the chore/finish-plans-7 branch November 20, 2026 06:31
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 this pull request may close these issues.

1 participant