On 2015-03-20 11:04, Michael Dürig wrote:
On 19.3.15 5:11 , Julian Reschke wrote:
- As far as I can tell, the reason why we even have Clock.Fast is the
assumption that Clock.SIMPLE (== System.currentTimeMillis()) may be
"slow". Does anybody know what exactly is the problem? (Because, after
all, the simplest possible fix would be to get rid of this apparently
fragile code)
We specifically introduced this to get around a performance regression.
See
https://issues.apache.org/jira/browse/OAK-1418?focusedCommentId=13923093&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13923093
OK, thanks for the context!
Best regards, Julian
