cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6609) Reduce Bloom Filter Garbage Allocation
Date Tue, 28 Jan 2014 12:54:38 GMT


Chris Burroughs commented on CASSANDRA-6609:

bq. actually improves performance by around 10-15%

That in a microbenchmark of the Bloom Filter or a full workload?

> Reduce Bloom Filter Garbage Allocation
> --------------------------------------
>                 Key: CASSANDRA-6609
>                 URL:
>             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

View raw message