You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "satish babu krishnamoorthy (Commented) (JIRA)" <ji...@apache.org> on 2011/11/08 08:34:53 UTC
[jira] [Commented] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146119#comment-13146119 ]
satish babu krishnamoorthy commented on CASSANDRA-3460:
-------------------------------------------------------
In what scenario are you planning to use sub-millisecond precision information
> Increase precision of elapsed time in casandra-cli
> --------------------------------------------------
>
> Key: CASSANDRA-3460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3460
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 1.0.2
> Reporter: Radim Kolar
> Priority: Minor
>
> Cassandra often return response in less then < 1 ms
> from another datacenter
> [default@test] get sipdb[23];
> Returned 0 results.
> Elapsed time: 219 msec(s).
> from own dataceter
> [default@test] get sipdb[13];
> Returned 0 results.
> Elapsed time: 0 msec(s).
> Precession of this timer needs to be increased a bit, while looking at network latency adding 1 number should be enough like : 0.2 ms should be sufficient.
> It would be good to display sub milliseconds only if time elapsed is < 1 ms.
--
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