cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Mazursky (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5581) Use System.nanoTime() to measure intervals
Date Tue, 21 May 2013 05:01:17 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mikhail Mazursky updated CASSANDRA-5581:
----------------------------------------

    Attachment: trunk-5581-v3.txt

v3 patch based on v2 - fixed missed nano->ms conversion in StorageService.joinTokenRing().
ReadCallback code from v2.
                
> Use System.nanoTime() to measure intervals
> ------------------------------------------
>
>                 Key: CASSANDRA-5581
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5581
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Mikhail Mazursky
>            Assignee: Mikhail Mazursky
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: 5581-v2.txt, trunk-5581.txt, trunk-5581-v3.txt
>
>
> System.nanoTime() should always be prefered to System.currentTimeMillis() to measure
time intervals. It's not affected by system clock adjustments & drift.
> While testing C* we found that it's very unstable if system clock drifts. Problems happen
even under low load with tiny dataset. In our case other VMs on the same hardware box produced
high CPU load and system clock drifted a lot in C* VMs. We fixed that but there is definitelly
room for improvement in C* itself.

--
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

Mime
View raw message