Connect shard throughput #5151
Closed
Connect shard throughput #5151
Conversation
This file contains 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
fulmicoton
force-pushed
the
connect-shard-throughput
branch
from
2a7d6ea to
038a316
Compare
fulmicoton
force-pushed
the
connect-shard-throughput
branch
from
038a316 to
edd6787
Compare
fulmicoton
commented
Jul 1, 2024
fulmicoton
force-pushed
the
connect-shard-throughput
branch
4 times, most recently
from
a43c7a7 to
76cc3d9
Compare
trinity-1686a
approved these changes
Jul 1, 2024
fulmicoton
force-pushed
the
connect-shard-throughput
branch
from
76cc3d9 to
b753a79
Compare
|
Closed and reopened as #5196 |
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.
Tested on simian with a pathologic workload:
On the left, without any per-shard weighting.
On the right, with per-shard weighting.
indexing throughput
cpu usage
