[CASSANDRA-21528] Avoid Kind.values() allocation when deserializing range tombstone markers#4952
Open
koo-taejin wants to merge 2 commits into
Open
[CASSANDRA-21528] Avoid Kind.values() allocation when deserializing range tombstone markers#4952koo-taejin wants to merge 2 commits into
koo-taejin wants to merge 2 commits into
Conversation
…ange tombstone markers
koo-taejin
changed the title
smiklosovic
self-requested a review
July 24, 2026 09:05
smiklosovic
approved these changes
Jul 24, 2026
…alization to avoid per-read array allocation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ClusteringPrefix.Kind.values() creates a new array on every call. This happens when Cassandra deserializes range tombstone markers.
I found this while using Temporal with Cassandra. Temporal uses many range deletes. In this workload, this array allocation was about 3% of the total memory allocations. This code also used noticeable CPU time.
Cache the values array to avoid this repeated work.
Thanks. :)
patch by koo.taejin; reviewed by for CASSANDRA-21528
The Cassandra Jira