As documented in the blog post *[Beware of System.nanoTime() in Java][1]*, on x86 systems, Java&#39;s System.nanoTime() returns the time value using a [CPU][2] specific counter. Now consider the following case I use to measure time of a call:

    long time1= System.nanoTime();
    foo();
    long time2 = System.nanoTime();
    long timeSpent = time2-time1;

Now in a multi-core system, it could be that after measuring time1, the thread is scheduled to a different processor whose counter is less than that of the previous CPU. Thus we could get a value in time2 which is *less* than time1. Thus we would get a negative value in timeSpent.

Considering this case, isn&#39;t it that System.nanotime is pretty much useless for now?

I know that changing the system time doesn&#39;t affect nanotime. That is not the problem I describe above. The problem is that each CPU will keep a different counter since it was turned on. This counter can be lower on the second CPU compared to the first CPU. Since the thread can be scheduled by the OS to the second CPU after getting time1, the value of timeSpent may be incorrect and even negative.

  [1]: http://www.principiaprogramatica.com/2008/04/25/beware-of-systemnanotime-in-java/
  [2]: http://en.wikipedia.org/wiki/Central_processing_unit


All Nanotime Solutions on Gang of Coders

Total of 1 Nanotime Solutions

Is System.nanoTime() completely useless?