client can use lz4 to compress request #89988
Open
+1,590
−18
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
elasticsearchmachine
added
external-contributor
wjp719
changed the title
kingherc
added
>enhancement
:Clients/Java Low Level REST Client
elasticsearchmachine
added
Team:Clients
|
Pinging @elastic/clients-team (Team:Clients) |
|
@jpountz can you help or find some one to review this pr, thanks. |
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.
now client can use gzip to compress request, but gzip is more cpu consuming, this pr add another choice to use lz4 to compress request.
In my test data, lz4 can compress data size to one fifth with 4% cpu overhead in client, while gzip can compress data size to one eighth with 17% cpu overhead. So LZ4 is more lightweight.