[
https://issues.apache.org/jira/browse/OAK-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977053#comment-13977053
]
Jukka Zitting commented on OAK-1757:
------------------------------------
Related comments in http://markmail.org/message/jhkvh2masdmvmlz6:
{quote}
> also, using a background task, that executes every MS is IMO a overhead.
Yes, but since it's a background task it won't block any client code.
The CPU overhead is also pretty low, much lower than calling the same
currentTimeMillis()/nanoTime() methods repeatedly in each
SessionDelegate.perform(). If this overhead does show up in a
benchmark, reducing the execution frequency should be fine as it would
only further reduce the accuracy of the gathered timing statistics.
{quote}
> Oak eats too many CPU cycles when idle
> --------------------------------------
>
> Key: OAK-1757
> URL: https://issues.apache.org/jira/browse/OAK-1757
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Michael Dürig
>
> An idle Oak eats roughly 5% of my CPU cycles.
> This is caused by the {{Clock}} implementations introduced at
> http://svn.apache.org/viewvc?view=revision&revision=1575050. Scheduling the
> fast clock to update its time every millisecond is quite expensive.
> Substituting for the simple clock reduces idle CPU usage to below 1%.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
