[
https://issues.apache.org/jira/browse/OAK-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978381#comment-13978381
]
Jukka Zitting commented on OAK-1757:
------------------------------------
bq. This is a quantisation effect, which is inherently non linear.
Right. My assumption here is that the start times of session operations have
little correlation with the clock update frequency, which seems like a
reasonable thing to assume or at least good enough for the purpose we're
gathering the statistics for. And if the operation start times do correlate
with the clock updates, then the measurement error is at most 1ms (or whatever
our update frequency is) per operation, which is also still reasonable.
bq. switch the respective statistics off and rethink our approach here.
That would also work, though the currently collected statistics _are_ useful so
we'd need something that's at least roughly as good.
> 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)
