On Mon, Oct 3, 2011 at 3:57 PM, Ramesh Natarajan wrote:
> Thanks Aaron. The ms in the latency is it microseconds or milliseconds?
> I ran the 2 commands at the same time. I was expecting the values to be in
> the some what similar but from my output earlier , you can see the median
> in read late
ms is for microseconds
To get a handle on what is happening I would run them both first to reset the
recent counts. Then run them and see if they make sense.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 4/10/2011, at 9:57 AM,
Thanks Aaron. The ms in the latency is it microseconds or milliseconds?
I ran the 2 commands at the same time. I was expecting the values to be in
the some what similar but from my output earlier , you can see the median
in read latency in histogram output is about 10 milliseconds whereas the
cfs
Hi Rameash,
Both tools output the "recent" latency, and while they do this slightly
differently, the result is that it's the latency since the last time it was
checked. Also the two tools use different counters, so using cfstats will not
update cfhistogram.
S
I am running a cassandra 0.8.6 cluster. I started a clean test setup and run
my tests for a while. Later when I run cfstats and cfhistograms ( both ran
at the same time )
the values for Read/Write latency doesn't match. As per cfstats the
latency for read and write are 5.086 and 0.018 ms respec
