perf(zero-cache): batch v6 websocket change frames - #9
Closed
Karavil wants to merge 1 commit into
Closed
Conversation
Why: reduce RM to serving-replica websocket overhead while preserving the v6 Downstream payload and per-message ACK semantics. * add stream batch frames and subscribeBatched for change streams * keep websocket batch boundaries visible through incremental sync worker flushing * update the rm-vs-load harness to benchmark websocket batch frames
Karavil
force-pushed
the
capy/rm-vs-load-v6-websocket-batches
branch
from
May 26, 2026 19:02
4a4431c to
9ca34bf
Compare
Owner
Author
|
Replaced by rocicorp/mono PRs rocicorp#6070 through rocicorp#6078. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what changed
Preserves the v6
Downstreampayload shape while allowing websocket batch frames andsubscribeBatched(). Incremental sync flushes the worker batch after a received websocket frame.ACK semantics stay per-message in this PR.
benchmark output
medium-wide-batch-pressure, 15s, compared to hot queue helpers:The ACK count rises because this PR intentionally keeps old v6 per-message ACK behavior while batching frames.
validation