Zstd experiment #4
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
…s events once, never decompress on the server
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.
Findings in this test conclude that enabling ZSTD compression for clients reduces BW per message by ~31.5% but increases CPU load an incredible amount.
In the below CPU profiles, Jetstream is serving from the playback buffer as fast as it can to a single client.
The CPU costs of compression seems too high for now for me to want to support. The bandwidth usage of Jetstream even with hundreds of consumers is still well below 1Gbps for now and running multiple instances makes it relatively easy to scale out Jetstream horizontally for more consumers if needed.
This was a fun experiment though!