[ 
https://issues.apache.org/jira/browse/CASSANDRA-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187169#comment-13187169
 ] 

Vijay edited comment on CASSANDRA-3723 at 1/16/12 8:42 PM:
-----------------------------------------------------------

>>> latency = await + this task's processing time, right?
Currently it is just the processing time... what i am proposing is to change 
the latency number to something like await (await in the queue + processing 
time). If that makes sense.

>>> not sure why we'd remove the latency though
I am not saying we have to remove it... Just like a enhancement instead of 
adding one more metric to glance :)
                
      was (Author: vijay2...@yahoo.com):
    >>> latency = await + this task's processing time, right?
Currently it is just the processing time... what i am proposing is to change 
the latency number to something like await. (If that makes sense).

>>> not sure why we'd remove the latency though
I am not saying we have to remove it... Just like a enhancement instead of 
adding one more metric to glance :)
                  
> Include await for the queues in tpstats
> ---------------------------------------
>
>                 Key: CASSANDRA-3723
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3723
>             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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to