would contact another host in
the ring to fetch the data.
Thanks,
Arindam
-Original Message-
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Wednesday, October 03, 2012 12:32 AM
To: user@cassandra.apache.org
Subject: Re: Read latency issue
Running a query to like select * from
by key which should
have been the fastest. I hope someone can help investigate or share numbers
from their tests.
Regards,
Roshni
From: dean.hil...@nrel.gov
To: user@cassandra.apache.org
Date: Tue, 2 Oct 2012 06:41:09 -0600
Subject: Re: Read latency issue
Interesting
...@nrel.gov
To: user@cassandra.apache.org
Date: Tue, 2 Oct 2012 06:41:09 -0600
Subject: Re: Read latency issue
Interesting results. With PlayOrm, we did a 6 node test of reading 100
rows from 1,000,000 using PlayOrm Scalable SQL. It only took 60ms. Maybe we
have better hardware though
another host in
the ring to fetch the data.
Thanks,
Arindam
-Original Message-
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Wednesday, October 03, 2012 12:32 AM
To: user@cassandra.apache.org
Subject: Re: Read latency issue
Running a query to like select * from table_name
To: user@cassandra.apache.org
Subject: RE: Read latency issue
Date: Wed, 3 Oct 2012 17:53:46 +
Thanks for your responses.
Just to be clear our table declaration looks something like this:
CREATE TABLE sessionevents (
atag text,
col2 uuid,
col3 text,
col4 uuid,
col5 text
data in some scenarios, and so need to optimize that scenario.
Thanks,
Arindam
From: Roshni Rajagopal [mailto:roshni_rajago...@hotmail.com]
Sent: Wednesday, October 03, 2012 4:53 PM
To: user@cassandra.apache.org
Subject: RE: Read latency issue
Hi Arindam,
There were some changes for CQL3
Interesting results. With PlayOrm, we did a 6 node test of reading 100 rows
from 1,000,000 using PlayOrm Scalable SQL. It only took 60ms. Maybe we have
better hardware though??? We are using 7200 RPM drives so nothing fancy on the
disk side of things. More nodes puts at a higher throughput
