RE: Worse perf after Row Caching version 1.2.5:

2014-02-13 Thread PARASHAR, BHASKARJYA JAY
Thanks a lot Marcus. That explains it. From: Marcus Eriksson [mailto:krum...@gmail.com] Sent: Thursday, February 13, 2014 12:33 AM To: user@cassandra.apache.org Subject: Re: Worse perf after Row Caching version 1.2.5: "select * from " will not populate row cache, but if the row is c

Re: Worse perf after Row Caching version 1.2.5:

2014-02-12 Thread Marcus Eriksson
le Switch Count: 0 > > Read Count: 0 > > Read Latency: NaN ms. > > Write Count: 0 > > Write Latency: NaN ms. > > Pending Tasks: 0 > > Bloom Filter False Positives: 0 > > Bloom Filter False Ratio: 0.0 > > Bloom Filter Space Used: 2232 &

RE: Worse perf after Row Caching version 1.2.5:

2014-02-12 Thread PARASHAR, BHASKARJYA JAY
Bloom Filter False Positives: 0 Bloom Filter False Ratio: 0.0 Bloom Filter Space Used: 2232 Compacted row minimum size: 61 Compacted row maximum size: 149 Compacted row mean size: 100 From: Jonathan Lacefield [mailto:jlacefi...@datastax.com] Sent: Tuesday, February 11, 2014 10:43 AM To:

Re: Worse perf after Row Caching version 1.2.5:

2014-02-11 Thread Jonathan Lacefield
Hello, Please paste the output of cfhistograms for these tables. Also, what does your environment look like, number of nodes, disk drive configs, memory, C* version, etc. Thanks, Jonathan Jonathan Lacefield Solutions Architect, DataStax (404) 822 3487

Worse perf after Row Caching version 1.2.5:

2014-02-11 Thread PARASHAR, BHASKARJYA JAY
Hi, I have two tables and I enabled row caching for both of them using CQL. These two CF's are very small with one about 300 rows and other < 2000 rows. The rows themselves are small. Cassandra heap: 8gb. a. alter table TABLE_X with caching = 'rows_only'; b. alter table TABLE_Y with c