Return-Path: 
 <dev-return-7158-apmail-cassandra-dev-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-dev-archive@www.apache.org
Delivered-To: apmail-cassandra-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2ABB8D34E
	for <apmail-cassandra-dev-archive@www.apache.org>;
 Wed, 22 Aug 2012 05:19:23 +0000 (UTC)
Received: (qmail 47954 invoked by uid 500); 22 Aug 2012 05:19:22 -0000
Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org
Received: (qmail 47787 invoked by uid 500); 22 Aug 2012 05:19:22 -0000
Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cassandra.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cassandra.apache.org>
List-Post: <mailto:dev@cassandra.apache.org>
List-Id: <dev.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list dev@cassandra.apache.org
Received: (qmail 47735 invoked by uid 99); 22 Aug 2012 05:19:20 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 05:19:20 +0000
X-ASF-Spam-Status: No, hits=1.7 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of amithanda01@gmail.com
 designates 209.85.220.172 as permitted sender)
Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com)
 (209.85.220.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 05:19:13 +0000
Received: by vcbfo14 with SMTP id fo14so668645vcb.31
        for <multiple recipients>; Tue, 21 Aug 2012 22:18:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=xvgg1bcAlWtSf3Ihq2qTb5CrZMvU8jdlceRLTFlS578=;
        b=EDzMmPQEPUDAEo1HjvbNa5Oqmuwq8gdOUuA0hJBbG8Okq0UmxIsx5tBnK1DSTXD+pZ
         vCrvjLKbssIuKJ5cmp5ttql/icVEDaDUk0QbnAMIUDZ/Ba16pJy3TeZFs33ZxjJbMXxI
         Jv0k2en3HGBKAyQPeAyzgMaaqGzeIubObCCwAqKPjnHU/8kldizGqaozBp6F6BaaUPo6
         tjKHmszyXj/YlaUiOF5SP/AZOvbkMogGWgxTNcDRq5ulTPl251C0K2liV+vArKqQokIJ
         37LZWz9i3OOqbMDZCVfkBBHXAe1HszC/6fKtc4fuPQMkNhv6Td4nCTXaOIZxCD7dXnZm
         uFcA==
MIME-Version: 1.0
Received: by 10.52.100.33 with SMTP id ev1mr13439260vdb.17.1345612732116; Tue,
 21 Aug 2012 22:18:52 -0700 (PDT)
Received: by 10.58.68.106 with HTTP; Tue, 21 Aug 2012 22:18:52 -0700 (PDT)
In-Reply-To: 
 <CALdd-zjsXZQULfzB1TxsujOLBO8_fppUDGZvWWTNHCy+WKH0hA@mail.gmail.com>
References: 
 <CAKBj7f=+c5udM9RAhxLT1hr94L__38AT64hAz+Q97dnsMD+-Jg@mail.gmail.com>
	<CALdd-zjsXZQULfzB1TxsujOLBO8_fppUDGZvWWTNHCy+WKH0hA@mail.gmail.com>
Date: Wed, 22 Aug 2012 10:48:52 +0530
Message-ID: 
 <CAKBj7fmHD1AyEOYQBL_CcQA3qDpZCVnkvi=tfGXA10HHcOt1qA@mail.gmail.com>
Subject: Re: Problem while configuring key and row cache?
From: Amit Handa <amithanda01@gmail.com>
To: dev@cassandra.apache.org, user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf3071c6eae72e9504c7d3e0d2

--20cf3071c6eae72e9504c7d3e0d2
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Thanks Jonathan for your reply.
I modified key_cache_size_in_mb and row_cache_size_in_mb values inside
cassandra.yaml. but not able to see it's effect using command " *./nodetool
-h 107.108.189.212 cfstats*". Can u let me know how to verify that the
setting for key_cache_size and row_chache_size has taken place.

With Regards,
Amit


On Tue, Aug 21, 2012 at 8:19 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> setcachecapacity is obsolete in 1.1+.  Looks like we missed removing
> it from nodetool.  See
> http://www.datastax.com/dev/blog/caching-in-cassandra-1-1 for
> background.
>
> (Moving to users@.)
>
> On Tue, Aug 21, 2012 at 8:19 AM, Amit Handa <amithanda01@gmail.com> wrote:
> > I started exploring apache cassandra 1.1.3. I am facing problem with how
> to
> > improve performance of cassandra using caching configurations.
> > I tried setting following configurations:
> >
> > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 200005 0
> > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 0 200005
> > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 200005
> 200005
> > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 444 444
> >
> >
> > But when i am checking that this particula configuration are really been
> > configured using command:
> > ./nodetool -h 107.108.189.212 cfstats
> >
> > it's showing following results for keySpace DemoUser and column Family
> > Users:
> > *Keyspace: DemoUser
> >     Read Count: 21914
> >     Read Latency: 0.08268495026010769 ms.
> >     Write Count: 87656
> >     Write Latency: 0.06009481381765082 ms.
> >     Pending Tasks: 0
> >         Column Family: Users
> >         SSTable count: 1
> >         Space used (live): 1573335
> >         Space used (total): 1573335
> >         Number of Keys (estimate): 22016
> >         Memtable Columns Count: 0
> >         Memtable Data Size: 0
> >         Memtable Switch Count: 1
> >         Read Count: 21914
> >         Read Latency: 0.083 ms.
> >         Write Count: 87656
> >         Write Latency: 0.060 ms.
> >         Pending Tasks: 0
> >         Bloom Filter False Postives: 0
> >         Bloom Filter False Ratio: 0.00000
> >         Bloom Filter Space Used: 41104
> >         Compacted row minimum size: 150
> >         Compacted row maximum size: 179
> >         Compacted row mean size: 179 *
> >
> > I am unable to see the effect of above setcachecapacity command. Let me
> > know how i can configure the cache capacity, and check it's effect.
> >
> > With Regards,
> > Amit
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>

--20cf3071c6eae72e9504c7d3e0d2--