Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 54355 invoked from network); 21 Jul 2010 06:35:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Jul 2010 06:35:32 -0000 Received: (qmail 6231 invoked by uid 500); 21 Jul 2010 06:35:31 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 6216 invoked by uid 500); 21 Jul 2010 06:35:29 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 6208 invoked by uid 99); 21 Jul 2010 06:35:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jul 2010 06:35:29 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 209.85.161.44 is neither permitted nor denied by domain of scode@scode.org) Received: from [209.85.161.44] (HELO mail-fx0-f44.google.com) (209.85.161.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jul 2010 06:35:20 +0000 Received: by mail-fx0-f44.google.com with SMTP id 1so3632552fxm.31 for ; Tue, 20 Jul 2010 23:35:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.248.3 with SMTP id a3mr707638mus.21.1279694100203; Tue, 20 Jul 2010 23:35:00 -0700 (PDT) Sender: scode@scode.org Received: by 10.103.240.3 with HTTP; Tue, 20 Jul 2010 23:35:00 -0700 (PDT) X-Originating-IP: [90.235.88.81] In-Reply-To: <201007211241415681672@aspire-tech.com> References: <3369e97d-ac19-e9d0-cc66-9a303b9e735c@me.com> <201007201447455523325@aspire-tech.com> <201007211241415681672@aspire-tech.com> Date: Wed, 21 Jul 2010 08:35:00 +0200 X-Google-Sender-Auth: 7BwOGk14598iL4RUrkI_IE6Mmxs Message-ID: Subject: Re: Re: What is consuming the heap? From: Peter Schuller To: user@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org > 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=C2=A0files in my keyspace, it's > 436,747,815bytes. > > I=C2=A0guess this means=C2=A0it=C2=A0won't consume a major part of 10g he= ap space Right, doesn't sound like bloom filters are the cause. Are you running with defaults settings otherwise - cache sizes, flush thresholds, etc? --=20 / Peter Schuller