Add option to gzip compress request bodies #239
Merged
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.
When sending large volumes of data to the
_bulk
API it can be significantly more efficient to compress the bodies of HTTP requests. Thanks to JSON's high compression rates, in my testing I can see over 90% reductions in payload size.Here are the first and last entires, along with two large payloads, from the same 744,057 document ingest run.
Uncompressed request body, total batch processing runtime: 6 minutes 37 seconds.
Gzip compressed request body, total ingest runtime: 1 minutes 52 seconds.
These payloads compressed exceptionally well, between 70-95% smaller. Because this was measured from a home ISP to the cloud, the total runtime was significantly more impacted by limited upload bandwidth than the target cluster's compute.
I've added a
request_body_compression
boolean to theTransportBuilder
which allows therequest_builder
to conditionally compresses the body's bytes and inject theContent-Encoding: gzip
header.