incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Schuller <peter.schul...@infidyne.com>
Subject Re: Re: What is consuming the heap?
Date Wed, 21 Jul 2010 06:35:00 GMT
> So the bloom filters reside in memory completely?

Yes. The point of bloom filters in cassandra is to act as a fast way
to determine whether sstables need to be consulted. This check
involves random access into the bloom filter. It needs to be in memory
for this to be effective.

But due to the nature of bloom filters you don't need a lot of memory
per key in the database, so it scales pretty well.

> I count the total size of *-Filter.db files in my keyspace, it's
> 436,747,815bytes.
>
> I guess this means it won't consume a major part of 10g heap space

Right, doesn't sound like bloom filters are the cause.

Are you running with defaults settings otherwise - cache sizes, flush
thresholds, etc?

-- 
/ Peter Schuller

Mime
View raw message