cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3723) Include await for the queues in tpstats
Date Mon, 16 Jan 2012 19:29:48 GMT


Peter Schuller commented on CASSANDRA-3723:

I'm very much +1 on await, including having it right there in tpstats (not just JMX), it's
a very useful metric (not sure why we'd remove the latency though).

As for performance: There are several things I've thought of that I want that are potentially
performance impactful, yet useful even if just probabilistically sampled. I think there's
a case to be made for using (thread-local, to avoid synchronization) randomization and probabilities
in collecting statistics. This is one such case, if indeed there is a significant performance
impact to begin with.
> Include await for the queues in tpstats
> ---------------------------------------
>                 Key: CASSANDRA-3723
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
> Something simillar to IOSTAT await, there is an additional over head not sure if we have
to make an exception for this.... but i think this has a huge "+" while troubleshooting....
> await
> The average time (in milliseconds) for I/O requests issued to the request to be served.
This includes the time spent by the requests in queue and the time spent servicing them 
> or we can also have a simple average of time spent in the queue before being served.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message