Repository navigation
Closed
Labels
app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)area/ciCI/CD pipelines, workflows, and build automation (area)CI/CD pipelines, workflows, and build automation (area)effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-inskind/performancePerformance problem or optimizationPerformance problem or optimizationmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addednowOrg Project gate: active priority — orchestrator adds to the boardOrg Project gate: active priority — orchestrator adds to the boardpriority/highImportant and time-sensitiveImportant and time-sensitivesource/humanFiled directly by a humanFiled directly by a humanstatus:done
Description
What and why
Benchmarks for guest replay of N events, journal append+fsync, checkpoint compaction and session fan-out to K clients, with committed baselines and a non-blocking CI job reporting >20% regressions. Several Phase 11/12 exits (fast CI lane, many worlds per node, fair scheduling) are stated as numbers, and nothing measures them today.
Source
Current status
Not started. No pkgs/id/benches directory; no bench/criterion in pkgs/id/Cargo.toml, justfile, flake.nix or .github/workflows/id*.yml (grep).
Acceptance criteria
- Benchmarks exist for guest replay of N events, journal append+fsync, checkpoint compaction and session fan-out to K clients
- Baselines are committed to the repo
- A non-blocking CI job runs the benchmarks and reports any regression over 20% against the baseline
- A
justrecipe and matchingnix run .#<cmd>app run them locally (pkgs/id/AGENTS.md keeps the two in sync)
Size
L
Prerequisites
None.
Metadata
Metadata
Assignees
Labels
app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)area/ciCI/CD pipelines, workflows, and build automation (area)CI/CD pipelines, workflows, and build automation (area)effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-inskind/performancePerformance problem or optimizationPerformance problem or optimizationmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addednowOrg Project gate: active priority — orchestrator adds to the boardOrg Project gate: active priority — orchestrator adds to the boardpriority/highImportant and time-sensitiveImportant and time-sensitivesource/humanFiled directly by a humanFiled directly by a humanstatus:done
Activity
docs(id): Phase 14 plan — close-out: finish, measure, verify, open th…
dezren39 commentedon Oct 26, 2026
Intake review
Verified still live on main
14dd66b6(2026-10-26, fleet monitor). There is nopkgs/id/benchesdirectory and nobench/criterionreference inpkgs/id/Cargo.toml— no benchmark harness or committed baselines exist yet.Related: prerequisite for #551 (fast CI lane exit is a number this harness would help prove); its measurements also underpin #557 (many worlds per node) and the fair-scheduling numbers in Phase 12.
Risks / suggested approach: the body's Size is L and the scope is four distinct benchmarks (guest replay, journal append+fsync, checkpoint compaction, session fan-out) — consider landing them as separable benches behind one harness so partial progress is committable. Keep the CI job non-blocking as specified, reporting >20% regressions against the committed baselines, and keep the
justrecipe andnix runapp in sync per pkgs/id/AGENTS.md.110 remaining items
dezren39 commentedon Oct 27, 2026
🤖 Agent note · picked up
wip(id): F11.8 slice 1 benchmark harness — four world benchmarks + ju…
dezren39 commentedon Oct 27, 2026
🤖 Agent note · done
id(ci): non-blocking benchmark regression reporting vs committed base…