Repository navigation
Reuse verified connections for wide object writes - #536
Merged
Merged
Conversation
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.
Summary
With default four-group concurrency, a cold 32-group write now establishes 32 data connections instead of 52.
Validation
cargo test -j1 --all-features --test object_writer_connections -- --test-threads=1— 21 passedcargo check -j1 --all-targets --all-features— passedcargo test -j1 --all-features --lib -- --test-threads=1— 726 passed, 33 ignored measurementsThe release workload wrote 64 initial 16 KiB objects at 15.2 objects/s and 16 post-failover objects at 32.1 objects/s, then verified all objects after total restart.