Thanks Aaron!
Through the commands "top" and "iostats", I find the IO system is not
overloaded yet. So I will check the data model.
And how to get the row size of a specific key? Do we have the api yet?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Sunday, May 22, 2011 at 6:15 PM, aaron morton w
It's hard to say the latency is to high without knowing how many columns and
how many bytes you are asking for. It's also handy to know what the query looks
like, i.e. is it a slice or a get by name, and the CF level
Latency reported at the CF or KS level are for local read / write operations.
What's your avg column size and row size? Your read latency in most case will
directly be related to how much you are trying to read. In my experience you
will see high read latency if you have big column size.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2
I use the default consistency level in the hector client, so it should be
QUORUM.
--
Dikang Gu
0086 - 18611140205
On Friday, May 20, 2011 at 4:25 PM, Jeffrey Kesselman wrote:
> What consistency are you asking for?
>
> On Fri, May 20, 2011 at 7:42 AM, Dikang Gu wrote:
> > Hi All,
> > I'm runni
What consistency are you asking for?
On Fri, May 20, 2011 at 7:42 AM, Dikang Gu wrote:
> Hi All,
> I'm running three cassandra 0.7.4 nodes in a cluster, and I give 2G memory
> to each node.
> Now, I get the cfstats here:
> Keyspace: UserMap
> Read Count: 38411
> Read Latency: 123.54214613001484 m
