Skip to content

perf(wal): coalesce overlapping quorum read rounds - #780

Draft
beinan wants to merge 4 commits into
lance-format:mainfrom
beinan:codex/wal-read-round-coalescing
Draft

beinan wants to merge 4 commits into
lance-format:mainfrom
beinan:codex/wal-read-round-coalescing

Conversation

@beinan

@beinan beinan commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Reads admitted in separate polls currently start separate quorum rounds even while an earlier round is still waiting for replies. Keep one unconfirmed round per group and collect later arrivals in the existing bounded, unsent batch. Issue that batch's fresh read-index barrier in the same poll that confirms the preceding round.

Later arrivals cannot use the preceding round's quorum. Request capacity, apply barriers, term checks and durable write acknowledgements remain unchanged. Leadership loss retires both the sent round and its queued successor.

The native regression admits 17 reads in separate polls while delaying the first quorum reply. Before this change it emits 17 read contexts; afterward it emits one, followed immediately by one fresh context. The first reply completes only the first read. All reads and another append finish, and all three original engines reopen with both full payloads.

Draft: a mixed ingestion, update and point-read run passed its full-value and bounded-progress checks, but did not show a meaningful throughput improvement; point-read tail latency and missed read arrivals worsened. Keep this PR in draft pending a better throughput/latency result. Coalescing overlapping rounds does not remove the need for fresh quorums on sequential reads or establish an end-to-end throughput gain.

Validation

  • Rust formatting check.
  • Release Clippy for all WAL service targets.
  • Release tests for all WAL service targets, including simultaneous sent/queued batch retirement on leadership loss.
  • Release WAL service build.

Refs #378.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant