[ https://issues.apache.org/jira/browse/CASSANDRA-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879070#comment-13879070 ]
Benedict commented on CASSANDRA-6609: ------------------------------------- Regrettably that isn't possible, as we need to return two values and there's no pass by reference available to us. We can't split the calculation up, unfortunately, either. > Reduce Bloom Filter Garbage Allocation > -------------------------------------- > > Key: CASSANDRA-6609 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6609 > Project: Cassandra > Issue Type: Improvement > Reporter: Benedict > Attachments: tmp.diff > > > Just spotted that we allocate potentially large amounts of garbage on bloom > filter lookups, since we allocate a new long[] for each hash() and to store > the bucket indexes we visit, in a manner that guarantees they are allocated > on heap. With a lot of sstables and many requests, this could easily be > hundreds of megabytes of young gen churn per second. -- This message was sent by Atlassian JIRA (v6.1.5#6160)