[ https://issues.apache.org/jira/browse/CASSANDRA-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-6609. --------------------------------------- Resolution: Fixed Fix Version/s: 2.0.5 Reviewer: Jonathan Ellis Assignee: Benedict Committed to 2.0. (1.2 is attractive but it's unquestionably an optimization and not a fix, so I'm not comfortable touching 1.2.) > Reduce Bloom Filter Garbage Allocation > -------------------------------------- > > Key: CASSANDRA-6609 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6609 > Project: Cassandra > Issue Type: Improvement > Reporter: Benedict > Assignee: Benedict > Fix For: 2.0.5 > > Attachments: tmp.diff, tmp2.patch, tmp3.patch > > > 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)