On 20.3.15 10:20 , Davide Giannella wrote:
On 20/03/2015 07:36, Julian Reschke wrote:
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.
Can we do a quick test? Let's put the scheduler to 15ms or 20ms and see
if it still fails for windows. AFAIR the purpose of Clock.FAST was to
have a non-accurate but fast clock.
There's even org.apache.jackrabbit.oak.stats.Clock#FAST_CLOCK_INTERVAL
for this.
Michael
