TL;DR. In a parallel build of 12 rustls worktrees on Linux x86_64, Cargo took 3 min 42 s and Mitts took 9.3 s . Shared caches were prewarmed and local target/ directories were empty; the initial warm-up build is excluded. Mitts reuses completed results across worktrees. Below are the measurement, the mechanism, and the cases where Cargo's cold or incremental builds win.
Cargo takes minutes. Mitts takes seconds.
For parallel work, the question is simple: when will the whole batch of builds be ready? The code is already split across branches. Now you need completed artifacts to move on to verification.
In The Hundred , twelve rustls worktrees on Linux x86_64 took 3 min 42 s with Cargo . With Mitts, 9.3 s . That is the completion time of the whole batch for one project, not a corpus total or the time of the first worktree to finish.
Figure 1. One heavy project from the study; medians of three repeats. Shared caches were prewarmed, local targets were empty.…