[
https://issues.apache.org/jira/browse/CASSANDRA-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694091#comment-13694091
]
Lior Golan commented on CASSANDRA-5014:
---------------------------------------
Why not keep the timeouts in millisecond (in the configuration) but make them
double, and then convert them to microseconds internally. This way you keep
compatibility with old timeout values while allowing users to set microsecond
level timeouts if they wish
> Convert timeout from milli second to micro second.
> --------------------------------------------------
>
> Key: CASSANDRA-5014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5014
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0 beta 1
> Reporter: Vijay
> Assignee: Vijay
> Priority: Trivial
> Fix For: 2.0 beta 1
>
> Attachments: 0001-CASSANDRA-5014.patch
>
>
> Convert all the timeouts to microseconds.
> Jonathan's comment from CASSANDRA-4705
> {quote}
> millis may be too coarse a grain here, especially for Custom settings.
> Currently an in-memory read will typically be under 2ms and it's quite
> possible we can get that down to 1 if we can purge some of the latency
> between stages. Might as well use micros since Timer gives it to us for free
> {quote}
--
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
