[jira] [Comment Edited] (CASSANDRA-9754) Make index info heap friendly for large CQL partitions

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617679#comment-14617679 ] 

Jonathan Ellis edited comment on CASSANDRA-9754 at 7/8/15 8:37 PM:
-------------------------------------------------------------------

But are most of those in the index summary (should be relatively stable once tenured) or the rowcache [Edit: meant key cache] (high churn)? 


was (Author: jbellis):
But are most of those in the index summary (should be relatively stable once tenured) or the rowcache (high churn)?

> 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
>            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)