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 <amithand...@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
