docs(bench): §9.19 — first D1/D2 soak record

[jensholdgaard]

What

The §9.19 benchmarks record for the first-ever RFC 0009 D1/D2 soak (run 29717165102, the #558 harness's maiden dispatch): one hour at 99,995 lines/s sustained, 360 M lines acked with zero failures.

• D2 PASS: max backlog 1 partition, 60 compactions, drained to zero — compaction keeps pace with sustained target-rate ingest.
• D1 recorded honestly as FAIL under per-core normalization (~25k lines/s/core on the 4-vCPU ci-runner) while the latency bar passes outright (ack p99 172.68 ms ≤ 200 ms) and the machine held the full 100k lines/s target. The record states the open maintainer reading explicitly: single-core-scaled bar (→ real 4× gap) vs per-node-on-baseline bar (→ the authoritative run decides). No bar was reworded to fit the result.
• §9.7's "the soak remains unrun" caveat now points forward to §9.19.

Doc-only; mdbook build verified. Curated by hand per the §9 discipline — no workflow writes §9.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WQY9wfrfRggqSpMLH8Xj3Y

[coderabbitai]

Warning

Review limit reached

@jensholdgaard, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 317652e2-b114-4f59-875b-904f6051c013

📥 Commits

Reviewing files that changed from the base of the PR and between 5242ab2 and 1d48d1e.

📒 Files selected for processing (1)

• docs/benchmarks.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bench-9-19-soak-record

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Records the first-ever RFC 0009 D1/D2 sustained-ingest soak run in docs/benchmarks.md (§9.19), and updates earlier benchmark narrative to point readers at the new soak results.

Changes:

• Adds §9.19 benchmark record for the first D1/D2 soak (indicative ci-runner run).
• Updates §9.7 narrative to reference the new §9.19 soak run record.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.