implement blob batching to improve EH sender throughput #275
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
…d downloading/deleting blobs destined for other clients
This was referenced Jul 8, 2023
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.
This PR implements a new mechanism for optimizing the EH sender throughput.
Previously we observed in multiple cases that the limited throughput when sending data to a single partition caused bottlenecks in the application (#268, #240).
With this new mechanism, anytime a partition sender needs to send large amounts of data (large messages, or many small messages), it does not send the messages directly via EH, but writes them to a blob batch, then sends a message containing the blob name. The receiver then loads the data from the blob batch.
This may also resolve #272 since it replaces some of the code that was identified as the likely source of the error.