cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9754) Make index info heap friendly for large CQL partitions
Date Thu, 09 Jun 2016 21:33:21 GMT

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

T Jake Luciani edited comment on CASSANDRA-9754 at 6/9/16 9:33 PM:
-------------------------------------------------------------------

[~mkjellman]  for a > 2.1 patch, take a look at CASSANDRA-7443 which added an abstraction
for IndexEntry and serializers which should hopefully be similar to what you did for this
2.1 version.  


was (Author: tjake):
[~mkjellman]  for a > 2.1 map take a look at CASSANDRA-7443 which added an abstraction
for IndexEntry and serializers which should hopefully be similar to what you did for this
2.1 version.  

> 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
>         Attachments: 9754_part1-v1.diff, 9754_part2-v1.diff
>
>
>  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)

Mime
View raw message