[
https://issues.apache.org/jira/browse/BOOKKEEPER-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417686#comment-13417686
]
Mridul Muralidharan commented on BOOKKEEPER-330:
------------------------------------------------
I should have raised the note in BOOKKEEPER-327.
In multi-core (and/or) multi-processor machines (particularly which are running
for long) this method is practically useless for fine measurement.
The precision ('fine') depends on a variety of factors I guess.
System.currentTimeMillis() is at lower resolution (and with time jumps, via ntp
updates, clock skew, etc) - but the measured difference would be what the
system 'thought' the time difference was : should average out to the same
(unless the nodes clock is chronically loosing time).
> System.currentTimeMillis usage in Hedwig
> ----------------------------------------
>
> Key: BOOKKEEPER-330
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-330
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-server
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Sijie Guo
> Assignee: Uma Maheswara Rao G
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-330.patch
>
>
> Need same changes in hedwig server as what did in bookkeeper as
> BOOKKEEPER-327.
--
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
