T3 Code · Performance over time
Heap after the last GC
All metrics
Heap after the last GC (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.
V8 heap used right after the window's last garbage collection.
Lower is better. No noise band measured yet, so no verdict.
- Unit
- MiB
- 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
- Every record, inside the agent ladder
- Upstream builds
- Every upstream build
- Source
none: OTLP heap gauge after the window's last GC (harness addition pending)
Heap after the last GC (lower is better) at 1 to 250 agents, Linux x64
against
Records, 50 agents
| Date | Tag | Median | Min to max | Valid | vs up to 7 previous | Verdict |
|---|
| No records at this level yet. |
Ladder as a table
| Agents | Nightly 17 Oct | Fork perf.9 |
|---|
| 1 | – | – |
| 50 | – | – |
| 100 | – | – |
| 150 | – | – |
| 200 | – | – |
| 250 | – | – |
Download this series