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/01/23 00:02:21 UTC
[jira] Created: (CASSANDRA-733) track latency in nanoseconds, not
milliseconds
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.
[jira] Updated: (CASSANDRA-733) track latency in nanoseconds, not
milliseconds
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-733:
------------------------------------
Attachment: 0001-track-microseconds.patch
> 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
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 0001-track-microseconds.patch
>
>
> 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.
[jira] Assigned: (CASSANDRA-733) track latency in nanoseconds, not
milliseconds
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek reassigned CASSANDRA-733:
---------------------------------------
Assignee: Gary Dusbabek
> 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
> Assignee: Gary Dusbabek
> 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.
[jira] Commented: (CASSANDRA-733) track latency in nanoseconds, not
milliseconds
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830164#action_12830164 ]
Jonathan Ellis commented on CASSANDRA-733:
------------------------------------------
+1
> 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
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 0001-track-microseconds.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-733) track latency in nanoseconds, not
milliseconds
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834874#action_12834874 ]
Hudson commented on CASSANDRA-733:
----------------------------------
Integrated in Cassandra #357 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/357/])
> 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
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 0001-track-microseconds.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-733) track latency in nanoseconds, not
milliseconds
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.