You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Radim Kolar (Created) (JIRA)" <ji...@apache.org> on 2011/11/06 20:51:51 UTC
[jira] [Created] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
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
[jira] [Updated] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "Radim Kolar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radim Kolar updated CASSANDRA-3460:
-----------------------------------
Attachment: cassandra-nanoseconds.txt
Display eta in 2 fraction digits, if total time is less then 10 ms.
> 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.11, 1.1.5
> Reporter: Radim Kolar
> Priority: Minor
> Labels: cli
> Attachments: cassandra-nanoseconds.txt
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3460:
--------------------------------------
Reviewer: yukim
Affects Version/s: (was: 1.1.5)
(was: 1.0.11)
Fix Version/s: 1.1.6
Assignee: Radim Kolar
> 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
> Reporter: Radim Kolar
> Assignee: Radim Kolar
> Priority: Minor
> Labels: cli
> Fix For: 1.1.6
>
> Attachments: cassandra-nanoseconds.txt
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "satish babu krishnamoorthy (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "Radim Kolar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146175#comment-13146175 ]
Radim Kolar commented on CASSANDRA-3460:
----------------------------------------
To estimate local network lags and server latency. Actually 2 digits would be better
For example 0.15 ms -> standard
0.35 ms -> LAN lags
0.85 ms -> sever lags
> 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
[jira] [Commented] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "Radim Kolar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148293#comment-13148293 ]
Radim Kolar commented on CASSANDRA-3460:
----------------------------------------
during latency testing i discovered that ideal will be to have sub millisecond latency rounded to 2 digits displayed if result is < 10 ms.
Because after cassandra heap gets more full, its latency is increased about 0.5 ms making result > 1 ms in most common cases for rows not found. Cassandra flush push latency under 1 ms again.
> 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
[jira] [Commented] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465169#comment-13465169 ]
Hudson commented on CASSANDRA-3460:
-----------------------------------
Integrated in Cassandra #2192 (See [https://builds.apache.org/job/Cassandra/2192/])
display elapsed time in 2 fraction digits in cli; patch by Radim Kolar, reviewed by yukim for CASSANDRA-3460 (Revision c7ce11f0031c81311a359de03380860fa4e366a5)
Result = ABORTED
yukim :
Files :
* src/java/org/apache/cassandra/cli/CliClient.java
* CHANGES.txt
> 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
> Reporter: Radim Kolar
> Assignee: Radim Kolar
> Priority: Minor
> Labels: cli
> Fix For: 1.1.6
>
> Attachments: cassandra-nanoseconds.txt
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3460) Increase precision of elapsed
time in casandra-cli
Posted by "Radim Kolar (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149080#comment-13149080 ]
Radim Kolar commented on CASSANDRA-3460:
----------------------------------------
while you are at it add support for timing row deletion too:
[default@rapidshare] del querycache['test'];
row removed.
[default@rapidshare] get querycache['test'];
> 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