okfgen: re-measure parallel `dotnet msbuild` queries now that E13 removed the obj/ collisions

Open
#172 0 comments 0 reactions 0 assignees View on GitHub

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

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

enhancement

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;
  • IntermediateOutputPath redirected 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.
  • StageDeadline is 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jchable/okf4net

All issues in jchable/okf4net

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.