T3 Code · Performance over time
Run update consumer backlog, max
All metrics
Run update consumer backlog, max (lower is better)
–
No records yet.
AgentsRange
When upstream merges a fix, the lines meet.
Upstream nightlyPerformance forkNoise bandRange of attempts▲▼ green = better, ▲▼ red = worse, beyond the noise band
As agents grow.
Largest backlog of run updates waiting for their consumer (fork releases and the weekly lane).
Lower is better. No noise band measured yet, so no verdict.
- Unit
- n
- Better
- lower
- Noise band
- none measured yet: no verdict
- Recorded from
- 20 Oct 2026; before that the series is a gap, never a zero
- Platforms
- Linux x64
- Lane
- Fork releases only
- Upstream builds
- Every upstream build
- Source
lagbench.json: backlog max
Run update consumer backlog, max (lower is better) at 1 to 250 agents, Linux x64
against
Records, 50 agents
Ladder as a table
Download this series
No series file yet.