You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2018/04/08 22:59:00 UTC
[jira] [Commented] (KAFKA-2607) Review `Time` interface and its
usage
[ https://issues.apache.org/jira/browse/KAFKA-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429906#comment-16429906 ]
Ismael Juma commented on KAFKA-2607:
------------------------------------
The following states that nanoTime and currentTimeMillis perform similarly on Linux:
http://pzemtsov.github.io/2017/07/23/the-slow-currenttimemillis.html
> Review `Time` interface and its usage
> -------------------------------------
>
> Key: KAFKA-2607
> URL: https://issues.apache.org/jira/browse/KAFKA-2607
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.11.0.0, 1.0.0
> Reporter: Ismael Juma
> Priority: Major
> Labels: newbie
>
> Two of `Time` interface's methods are `milliseconds` and `nanoseconds` which are implemented in `SystemTime` as follows:
> {code}
> @Override
> public long milliseconds() {
> return System.currentTimeMillis();
> }
> @Override
> public long nanoseconds() {
> return System.nanoTime();
> }
> {code}
> The issue with this interface is that it makes it seem that the difference is about the unit (`ms` versus `ns`) whereas it's much more than that:
> https://blogs.oracle.com/dholmes/entry/inside_the_hotspot_vm_clocks
> We should probably change the names of the methods and review our usage to see if we're using the right one in the various places.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)