Add support for message compression #63
Open
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.
Problem statement
For some workflows using RabbitMQ, performance gains can be realized by first compressing messages, sending them, and then decompressing the messages. In testing, it was shown that the amount of time between a message being sent and the publisher ack being received can decrease by up to 40%, with the performance gain being greater the more compressible and larger the message is.
Proposed changes
Message transformers are added to allow for modifications to messages during the producer's send and consumer's handle functions. Compression (using zstd as the underlying compression algorithm) is added as one such transformer.
Remaining work