You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
regions: Connections step cap is hit on real data; measure route-snapshot memory (follow-ups to #505) #508
Follow-ups from the #505 review (see the review comment on #505).
The step cap is hit on real data. On staging (48 h retention), /api/regions/routes reports steps: 5000, stepsTruncated: true. meshview-pve (168 h) will be truncated even more, so directed steps are effectively always incomplete. Aggregate step counts per (from, to, scope) across the horizon before capping, or use a size-based budget or a higher cap with a measured payload limit. Today's payload is 5.4 MB raw / 679 KB gzip.
Memory. Container RSS on staging was ~1.72 GiB with feat(regions): explore shared history and observed directed routes #505, against ~1.55 GiB on comparable deploys. Measure the route snapshot's retained size and add it to the memory diagnostics, because production hosts are smaller (meshview.dk: 3.7 GiB RAM shared with other services).
Addendum from the #507 staging check: besides the directed-step cap, the membership capture budgetmaxRegionsRoutePaths = 250000 (distinct paths, global) is also exhausted on real data. With 48 h retention and about 805k observations, coverage.evidence.capped = 1114 in #dk across 17 of 20 hours. Health and Timeline rates for #dk and "all scopes" are withheld as a result. Redesign the budgets so that a 168 h retention (meshview-pve) is not capped on our network: aggregate per (relay, scope, hour) before storing paths, or use per-scope or per-hour budgets. Treat this as a blocker for the next release that includes the Regions views.
Fixed by #510 (merged as 6fe9603a717d504a79c391a3982229bc588e1be5).Fixed by #510: Regions capture budgets fit real traffic (per-transmission paths 4096, per-hour budgets, step cap redesigned), with diagnostics for every limit. Verified on staging: capped 0, steps not truncated, RSS ~1.5–1.7 GiB. APPROVE, CI green.
Activity
dborup commentedon Oct 20, 2026
Addendum from the #507 staging check: besides the directed-step cap, the membership capture budget
maxRegionsRoutePaths = 250000(distinct paths, global) is also exhausted on real data. With 48 h retention and about 805k observations,coverage.evidence.capped = 1114in#dkacross 17 of 20 hours. Health and Timeline rates for#dkand "all scopes" are withheld as a result. Redesign the budgets so that a 168 h retention (meshview-pve) is not capped on our network: aggregate per (relay, scope, hour) before storing paths, or use per-scope or per-hour budgets. Treat this as a blocker for the next release that includes the Regions views.reviewfix(regions): drop the global capture ceiling, expose capture h…
dborup commentedon Oct 20, 2026
Fixed by #510 (merged as
6fe9603a717d504a79c391a3982229bc588e1be5).Fixed by #510: Regions capture budgets fit real traffic (per-transmission paths 4096, per-hour budgets, step cap redesigned), with diagnostics for every limit. Verified on staging: capped 0, steps not truncated, RSS ~1.5–1.7 GiB. APPROVE, CI green.