T3 Code · Performance over time
Main-thread gap after descendant polls, growth
All metrics
Main-thread gap after descendant polls, growth (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.
Growth per hour of the main-thread gap after each poll of descendant processes.
Lower is better. No noise band measured yet, so no verdict.
- Unit
- ms/h
- Better
- lower
- Noise band
- none measured yet: no verdict
- Recorded from
- 17 Oct 2026; before that the series is a gap, never a zero
- Platforms
- Linux x64
- Lane
- The weekly long-run lane, which starts after launch
- Upstream builds
- Every upstream build
- Source
server.trace.ndjson: gap after process polls, fitted slope (weekly lane)
Main-thread gap after descendant polls, growth (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.