Hello,
I have a question about CQL memory usage. I am currently using 1.2.9.
If I have a Cassandra table like this (created using Astyanax API):
CREATE TABLE table_name (
key text,
column1 text,
value blob,
PRIMARY KEY (key, column1)
) WITH COMPACT STORAGE;
and I run a query like this:
ance.
>
> is that a fair statement?
>
>
> From: Jonathan Ellis [jbel...@gmail.com]
> Sent: Thursday, March 25, 2010 8:01 PM
> To: user@cassandra.apache.org
> Subject: Re: memory question
>
> Cassandra mmaps your data files which show up as
Ellis [jbel...@gmail.com]
Sent: Thursday, March 25, 2010 8:01 PM
To: user@cassandra.apache.org
Subject: Re: memory question
Cassandra mmaps your data files which show up as RES and SHR. This is normal.
c0d1p1 is completely maxed out. Assuming that is your data disk and
not your commitlog one, you
Cassandra mmaps your data files which show up as RES and SHR. This is normal.
c0d1p1 is completely maxed out. Assuming that is your data disk and
not your commitlog one, you need to tell Cassandra to cache more rows
(or keys, depending).
If you are maxing out your caches and still seeing this t
no compaction.
Jonathan Ellis wrote:
did you check jmx to see if a compaction is going on?
On Mon, Mar 22, 2010 at 5:14 PM, Todd Burruss wrote:
after running my cluster for a while performance has become unacceptable,
200+ ms for reads. if running well, i see reads <10ms. when i run iost
did you check jmx to see if a compaction is going on?
On Mon, Mar 22, 2010 at 5:14 PM, Todd Burruss wrote:
> after running my cluster for a while performance has become unacceptable,
> 200+ ms for reads. if running well, i see reads <10ms. when i run iostat
> the disk is being hammered by reads
after running my cluster for a while performance has become unacceptable, 200+
ms for reads. if running well, i see reads <10ms. when i run iostat the disk
is being hammered by reads. seems like i/o caching isn't even being used
avg-cpu: %user %nice %system %iowait %steal %idle
