Lab / / benchmark
Five minutes in, less heap than at the start
A five-minute soak at 30 fps over a 5% lossy, reordering link moved 31,815 packets with zero holes and ended with managed heap 0.9% below where it started.
WebRTC, Measurement methodologyKeryx- Machine
- UNKNOWN — not stated
- Commit
- `cacb70c`, 2026-08-25
- Duration and rate
- 5 minutes at 30 fps
- Link
- 5% lossy, reordering
- Packets
- 31,815
- Repaired
- 1,564
- Holes
- 0
- History misses
- 0
- Managed heap at end
- 0.9% below where it started
Five minutes of 30 fps video across a 5% lossy, reordering link. 31,815 packets, 1,564 repaired, zero holes, zero history misses. Managed heap at the end was 0.9% below where it started.
The heap figure is the one worth naming. A five-minute soak that ends with less heap than it started is a statement that the steady state has no slow leak, and that the pooling works. The byte count moved in the direction the design intended, and it moved there without a forced collection.
What I read this as
I read 0.9% below as no growth rather than as a heap that shrinks over time. A managed runtime is free to return memory to the operating system or to hold a smaller live set at the end of a run, so the sign is not by itself a performance claim. What it does establish is the absence of the thing a soak exists to find, which is a per-packet allocation that accumulates.
| Metric | Value |
|---|---|
| duration / rate | 5 minutes at 30 fps |
| link | 5% lossy, reordering |
| packets | 31,815 |
| repaired | 1,564 |
| holes | 0 |
| history misses | 0 |
| managed heap at end | 0.9% below start |