Github user elyograg commented on the issue:
https://github.com/apache/lucene-solr/pull/294
Java programs are migrating to nanoTime instead of currentTimeMillis for
elapsed time because many people have found that the latter will go *backwards*
on occasion. It is not monotonic.
Using nanoTime should be far less likely to go backwards. That undesirable
behavior has been observed in the wild, but should be rare. Supposedly
nanoTime is monotonic if the OS properly supports a monotonic clock. There's a
lot of info out there about it:
https://www.google.com/search?q=java+nanotime+monotonic
The fact that nanoTime *might* produce elapsed times with greater accuracy
than one millisecond is a bonus.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
