On 2015-03-20 01:48, Alexander Klimetschek wrote:
AFAIK, this is expected, on Windows (or some Windows versions),
System.currentTimeMillis() only has a resolution of 15ms
http://stackoverflow.com/questions/7859019/system-currenttimemillis-is-not-accurate-on-windows-xp
Cheers,
Alex
That's not really true, see
<http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201403.mbox/%[email protected]%3E>
- you need to distinguish the clock (which can be as "good" as 1ms, see
above mail), from timers.
Anyway, it seems to me that Clock.Fast can't be made to work reliably,
and also that we really don't understand the reason why we don't simply
use Clock.SIMPLE. We currently use Clock.Fast in RepositoryImpl and
StopWatchLogger; we should have a look at these uses, and decide whether
we can switch to Clock.SIMPLE.
Best regards, Julian
