Thanks for the probing questions. Just got around to looking into this a
bit more and discovered it's not exactly what I thought. It's actually a
single multiget_slice with a fairly slow response time.
I've answered as many of the questions as I can, and have also included a
reply to Rob's state
On Fri, Feb 4, 2011 at 11:13 AM, Dan Kuebrich wrote:
> Is 2 seconds the normal "I went to disk" latency for cassandra?
Cassandra exposes metrics on a per-CF basis which indicate latency.
This includes both cache hits and misses, as well as requests for rows
which do not exist. It does NOT include
What operation are you calling ? Are you trying to read the entire row back?
How many SSTables do you have for the CF? Does your data have a lot of
overwrites ? Have you modified the default compaction settings ?
Do you have row cache enabled ?
How long does the second request take ?
Can you
Hi all,
It often takes more than two seconds to load:
- one row of ~450 events comprising ~600k
- cluster size of 1
- client is pycassa 1.04
- timeout on recv
- cold read (I believe)
- load generally < 0.5 on a 4-core machine, 2 EC2 instance store drives for
cassandra
- cpu wait generally < 1%
O
