PQ: avoid deserialization cost (POC) #17820
Draft
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.
What does this PR do?
Avoids deserialization cost of events passing through the PQ when memory pressure is absent, by maintaining a list of soft-references to the events added to each PQ page. When constructing batches during reads, we use a new internal intermediate type
BoxedQueueable
, each of which holds either a strong-reference to aQueueable
or thebyte[]
and deserializer necessary to construct it. Deserialization, if any, still occurs outside of the Queue locking mechanism.Why is it important/What is the impact to the user?
Reduces the overhead of reading from a PQ when a pipeline is staying caught up with the workload.
Status
This is a proof-of-concept; actual implementation may change significantly. As a proof-of-concept spike, I did not take the time to arrange it into bite-size changes.