okfgen: re-measure parallel `dotnet msbuild` queries now that E13 removed the obj/ collisions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- build-system, performance
Research direction
Start with the roadmap entry in ROADMAP.md and the code that runs the parallel dotnet msbuild query loop. Measure the query again after E13, and check how StageDeadline is accessed and whether repository MSBuild logic may write files during evaluation. Done means there is evidence about performance and safety sufficient to decide whether parallel queries can be revisited.
Written by the indexing model from the issue text.
Description
Extracted from ROADMAP.md (producer, "Measured and dropped: parallel dotnet msbuild queries").
Parallel queries were dropped on 2026-09-15. They were 37–40 % faster, but on a cold tree they lost projects to MSB3491 write collisions in a shared referenced project's obj/, and they did it silently: the run still exited 0.
E13 met the precondition:
-p:BuildProjectReferences=false;IntermediateOutputPathredirected into producer-owned scratch.
A query now builds nothing and writes no file into the scanned repository's obj/.
Before revisiting
- Measure again. The old timings were for a query that built its whole reference closure, which is code that no longer exists.
StageDeadlineis not thread-safe. It is consulted per project inside the query loop.- No one has shown that it is safe to run a repository's own MSBuild logic as several copies at once. A query evaluates that logic, and it can write wherever it likes.
- Dominant language
- C#
- Stars
- 4
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jchable/okf4net
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
umbraco/Umbraco-CMS#24668 · 1 comment ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7956 ·
Maintainers usually reply within 1 day