windsock: measure consume latency #1753
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.
Updates to latest windsock, making use of the new consumer latency functionality.
To calculate the consumer latency we:
SystemTime
in the first 12 bytes of the produced record payloadSystemTime
then call.elapsed()
to determine the amount of time passed.This matches the behaviour of rdkafka_performance: https://github.com/confluentinc/librdkafka/blob/master/examples/rdkafka_performance.c
I did not use a serialization library for this as I need to ensure they fit exactly into 12 bytes so we know what our minimum size of payload needs to be.
As a result of the new minimum of 12 bytes, the existing 1B bench case was turned into a 12B bench case.