You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/04/24 12:53:17 UTC

[jira] [Comment Edited] (OAK-1757) Oak eats too many CPU cycles when idle

    [ https://issues.apache.org/jira/browse/OAK-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979555#comment-13979555 ] 

Michael Dürig edited comment on OAK-1757 at 4/24/14 10:51 AM:
--------------------------------------------------------------

Fixed for 1.0 at http://svn.apache.org/r1589660 by setting the default clock update frequency to 100Hz. This reduces CPU usage from 5% to around 1% on my machine. 

I left the default clock update frequency at 1kHz on the trunk because of the impact on the statistics, which we should address in a follow up issue. 

See OAK-1767


was (Author: mduerig):
Fixed for 1.0 at http://svn.apache.org/r1589660 by setting the default clock update frequency to 100Hz. This reduces CPU usage from 5% to around 1% on my machine. 

I left the default clock update frequency at 1kHz on the trunk because of the impact on the statistics, which we should address in a follow up issue. 

> 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
>            Assignee: Michael Dürig
>             Fix For: 1.0
>
>
> 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)