draft: experiment with compressing the persistent queue data #17128
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.
since compression can be quite cheap compared to i/o, maybe we could default to compressing the data being written to the PQ.
this is a draft and shows a significant performance in performance, moving the bottleneck closer to the cbor mapper deserialization instead of PQ writing in my local laptop.
such a change must be however evaluated as to not introduce breaking changes, potentially with a V3 PQ format.
code-wise Logstash::Event could move to a extension of the Queueable interface that allows compression.