[ 
https://issues.apache.org/jira/browse/JCR-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525529
 ] 

Raffaele Sena commented on JCR-1112:
------------------------------------

I can reproduce this problem or something related to this by simply importing 
an XML file with a few thousand nodes. The more nodes I have in the repository 
and the more time the system spend in rebalancing the cache, pretty much at 
every access to the repository.

I was experimenting with a system with a simple hierarchical structure like:

/users
  user1
  user2
  user3

for each user I had a large data structure stored as XML (like an imported XML 
file)

with such a system, even with only a few users, accessing to the node 
/users/<userX> takes seconds (and the more users or complex structure I have 
the longer it takes) and all I see in the logs is resizeAll() messages



> CacheManager interval between recalculation of cache sizes should be 
> configurable
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-1112
>                 URL: https://issues.apache.org/jira/browse/JCR-1112
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: core
>            Reporter: Przemo Pakulski
>            Priority: Minor
>         Attachments: JCR-1112.txt
>
>
> Currently interval between recaluclation of cahce size is hard coded to 1000 
> ms. Resizing/recalculation of cache size is quite expensive method 
> (especially getMemoryUsed on MLRUItemStateCache is time consuming)
> Depending on the configuration, we realized that under some load up to 10-15% 
> percent of CPU time (profiler metrics) could be spend doing such 
> recalculations. It does not seem to be needed to resize cache every second. 
> Best this interval should be configurable in external config. file with other 
> cache settings (like memory sizes).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to