[
https://issues.apache.org/jira/browse/CASSANDRA-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189407#comment-15189407
]
Jack Krupansky commented on CASSANDRA-9754:
-------------------------------------------
Is this issue still considered a Minor priority? Seems like a bigger deal to
me. +1 for making it a Major priority - unless there is a longer list of even
bigger fish in the queue.
Just today there is a user on the list struggling with time series data and
really not wanting to have to split a partition that he needs to be able to
scan. Of source, scanning a super-wide partition will still be a very bad idea
anyway, but at least more narrow scans would still be workable with this
improvement in place.
Is this a 3.x improvement or 4.x or beyond? +1 for 3.x (3.6? 3.8?).
> Make index info heap friendly for large CQL partitions
> ------------------------------------------------------
>
> Key: CASSANDRA-9754
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9754
> Project: Cassandra
> Issue Type: Improvement
> Reporter: sankalp kohli
> Assignee: Michael Kjellman
> Priority: Minor
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
