[
https://issues.apache.org/jira/browse/CASSANDRA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916184#action_12916184
]
Jonathan Ellis commented on CASSANDRA-1555:
-------------------------------------------
bq. 90GB is way too early to be degrading performance
Well, that depends. If we're "degrading" from 6.71e-05 to 0.00108 FP to save
memory, then yes, that's definitely the right thing to do or even a 16GB heap
will get exhausted pretty quickly. But if we're having to degrade to > 1% FP
then that would be something to address.
> Considerations for larger bloom filters
> ---------------------------------------
>
> Key: CASSANDRA-1555
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1555
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Stu Hood
> Fix For: 0.8
>
>
> To (optimally) support SSTables larger than 143 million keys, we need to
> support bloom filters larger than 2 GB, which java.util.BitSet can't handle
> directly.
> A few options:
> * Switch to a BitSet class which supports 2^63 bits (Lucene's OpenBitSet)
> * Partition the java.util.BitSet behind our current BloomFilter
> ** Straightforward bit partitioning: bit N is in bitset N // 2^31
> ** Separate equally sized complete bloom filters for member ranges, which can
> be used independently or OR'd together under memory pressure.
> All of these options require new approaches to serialization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
