Repository navigation
Commit 0b107b5
perf(autobahn): raise the lane capacity to 60 blocks (#4632)
**Problem**
- `avail.BlocksPerLane` (30) bounds each lane's unexecuted blocks, freed
only by local execution and the local AppQC.
- At full load producers stall on lane capacity, lane blocks arrive in
bursts, and roadblocks become few and large, so execution has little
queued to overlap.
**Change**
- Raise `BlocksPerLane` from 30 to 60 (6 × `MaxLaneRangeInProposal`).
- A committee-sized bound was considered; per review it needs more
thought for dynamic committees, so this keeps a constant.
**Impact** (CLOB benchmark, 8 validators, same build, only the lane
bound changed)
- About +50% chain throughput against 30; 100 and 1000 measured the same
as 60.
- No lane-capacity waits, no mempool-full refusals, about 6x more
roadblocks per second, and about 4x lower p99 execute latency.
**Risk**
- Memory and disk: up to 60 unpruned blocks per lane, held for every
lane: about 120 MB per lane worst case at the 2 MB block limit.
- Rollback: a node holding more than 30 unpruned blocks on a lane fails
`restoreBlocks` on an older binary until its WAL drains.
**Tests**
- `avail`, `producer` and `p2p/giga` pass with `-race`.
Co-authored-by: Cursor <cursoragent@cursor.com>1 parent 3cb50e7 commit 0b107b5
1 file changed
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
25 | | - | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
26 | 28 | | |
27 | 29 | | |
28 | 30 | | |
| |||
0 commit comments