[
https://issues.apache.org/jira/browse/OAK-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977494#comment-13977494
]
Jukka Zitting commented on OAK-1757:
------------------------------------
bq. The 1ms resolution of the timer is too low as many of the operations take
sub milliseconds to execute.
The statistics are in any case aggregated over all session operations, so the
granularity of individual measurements is not that significant as long as the
average remains correct. That's also why I wouldn't mind reducing the clock
update frequency from 1000Hz to something like 100Hz or even 50Hz.
> 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)
