You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/02/04 18:04:27 UTC

[jira] Commented: (CASSANDRA-733) track latency in nanoseconds, not milliseconds

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

Jonathan Ellis commented on CASSANDRA-733:
------------------------------------------

possibly we want to measure w/ nanotime but store in microseconds so we get more mileage out of our Long counters (LatencyTracker & friends)

> track latency in nanoseconds, not milliseconds
> ----------------------------------------------
>
>                 Key: CASSANDRA-733
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-733
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6
>
>
> many ops finish in <1ms so presenting as ms ("0") isn't very useful.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.