Initial size of ConcurrentCache depends on number of segments (available processors)
------------------------------------------------------------------------------------
Key: JCR-2770
URL: https://issues.apache.org/jira/browse/JCR-2770
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-core
Reporter: Marcel Reutegger
Priority: Minor
This causes a build failure on my machine. Tests run into an OOME because the initial memory footprint of a ConcurrentCache on my machine is 8k. Many of the tests keep references to some kind of repository objects (node, session, x-manager), which means ConcurrentCache instances cannot be garbage collected immediately after a test run.
I think the overall initial size of the cache should be independent of the number of segments. See proposed patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.