Details
-
Improvement
-
Status: Awaiting Feedback
-
Low
-
Resolution: Unresolved
-
None
Description
Looking at a heap dump of 2.0 cluster, I found that majority of the objects are IndexInfo and its ByteBuffers. This is specially bad in endpoints with large CQL partitions. If a CQL partition is say 6,4GB, it will have 100K IndexInfo objects and 200K ByteBuffers. This will create a lot of churn for GC. Can this be improved by not creating so many objects?
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-8931 IndexSummary (and Index) should store the token, and the minimal key to unambiguously direct a query
-
- Open
-
-
CASSANDRA-11206 Support large partitions on the 3.0 sstable format
-
- Resolved
-
- relates to
-
CASSANDRA-9738 Migrate key-cache to be fully off-heap
-
- Resolved
-
-
CASSANDRA-9843 Augment or replace partition index with adaptive range filters
-
- Open
-
-
CASSANDRA-9231 Support Routing Key as part of Partition Key
-
- Resolved
-
- supercedes
-
CASSANDRA-13973 IllegalArgumentException in upgradesstables compaction
-
- In Progress
-