perf(aws): Reduce Aggregated Kinesis Record Size #147
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.
Description
PutRecord
call withPutRecords
Motivation and Context
Kinesis Data Streams charge based on PUT payload units, which have a minimum size of 25 KB. Historically the project aggregated up to the Kinesis limit of 1 MB because there was no support for the
PutRecords
API, but as of v1.0 there is. There's little (or no) value in sending aggregated records larger than 25 KB and by sending them viaPutRecords
the throughput performance increases by ~33% to ~50% (see screenshot).How Has This Been Tested?
This was tested on a high-volume, production data pipeline.
Types of changes
Checklist: