[JCR-2770] Initial size of ConcurrentCache depends on number of segments (available processors)

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0.3, 2.1.2, 2.2
• Component/s: jackrabbit-core
• Assignee: Jukka Zitting
• Reporter: Marcel Reutegger
• Created: 06/Oct/10 11:49
• Updated: 23/Sep/11 14:23
• Resolved: 13/Oct/10 13:13

Description

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.