[
https://issues.apache.org/jira/browse/JCR-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525013
]
Thomas Mueller commented on JCR-1112:
-------------------------------------
For certain use cases, 10 seconds delay may result in OutOfMemoryException. I'm
not against applying this patch, but we need to be sure it doesn't render the
CacheManager ineffective.
> under some load
Is there a way to reproduce this problem using a simple test application? If
not, I like to write one. To do that, I need some more information: How many
sessions, how much memory is available / used (java -Xmx...), what is the
algorithm, is XA used, versioning, how do the nodes look like, how does the
data look like, virtual machine, operating system?
> up to 10-15% percent of CPU time (profiler metrics)
How was this measured?
Thanks,
Thomas
> 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.
