[
https://issues.apache.org/jira/browse/CASSANDRA-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550920#comment-15550920
]
Michael Kjellman commented on CASSANDRA-9754:
---------------------------------------------
I'm a bit late on my Tuesday target I was aiming for on Saturday but for good
reason :) I've been working almost non-stop since (went to bed at 3:30am and
was up at 8:30am looking at graphs.. and I've been looking at graphs ever
since). I have a performance load running in 3 perf clusters -- I'd like to
aggregate those objective findings tomorrow and then push up whatever the state
of things is (it's *very* stable so I'm pretty pumped about that) along with
some benchmarks (the good and possibly bad/still needs improvement).
> 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
> Fix For: 4.x
>
> 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)
