chore: upgrade oxia-client to 0.9.3 - #37
Merged
Merged
Conversation
0.9.3 makes write batching rate-adaptive: a bounded per-shard in-flight window (maxWriteBatchesInFlight, default 4) holds batches open while the window is exhausted, so under server saturation batches grow toward maxRequestsPerBatch instead of flooding the write stream with ~5-put requests. This directly addresses the write-throughput wall measured in the cluster benchmarks (per-shard replication rounds carrying ~4.5 puts, ~56k w/s ceiling at 70% CPU). No code changes needed: the default window applies, and there are no breaking API changes. Signed-off-by: Matteo Merli <mmerli@apache.org>
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
1 participant
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.
Bump
io.github.oxia-db:oxia-client0.9.2 → 0.9.3.0.9.3 makes write batching rate-adaptive (#360): a bounded per-shard in-flight window (
maxWriteBatchesInFlight, default 4) holds batches open while the window is exhausted, so under server saturation batches grow towardmaxRequestsPerBatchinstead of flooding the stream with tiny requests.This is exactly the fix for the write-throughput wall diagnosed with this benchmark on a real 3-node cluster: server-side
kv_batch_countshowed ~4.5 puts per batch regardless of load, leaving the write path bound by per-shard replication rounds (~56–63k w/s ceiling at 70% server CPU and ~25% disk utilization, with pure queueing beyond that). With the window, the same serialized rounds carry up to ~1000 ops each.No benchmark code changes needed: the default window applies through the existing driver, and 0.9.3 has no breaking API changes.
Verification
./gradlew build shadowJarpasses (resolves 0.9.3, compiles, tests green).Follow-up after merge: rebuild the worker image (
merlimat/oxia-bench:1.0-test-5) and re-run the max-throughput sweep to measure the wall moving.