cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-5014) Convert timeout from milli second to micro second.
Date Thu, 27 Jun 2013 05:42:21 GMT


Vijay updated CASSANDRA-5014:

    Attachment: 0001-CASSANDRA-5014-v2.patch

I like the double idea and hence the attached patch uses double instead of long.

PS: getSnapshot().getValue(retryPolicy.value) returns percentile in milliseconds but the code
before this patch assumed microsecond... this patch also fixes it.
> Convert timeout from milli second to micro second.
> --------------------------------------------------
>                 Key: CASSANDRA-5014
>                 URL:
>             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, 0001-CASSANDRA-5014-v2.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:

View raw message