You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/08/08 16:57:44 UTC
[jira] Commented: (JCR-1715) Prevent excessive Path.Element
instances
[ https://issues.apache.org/jira/browse/JCR-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620945#action_12620945 ]
Marcel Reutegger commented on JCR-1715:
---------------------------------------
A note on the Path.Element cache in PathFactoryImpl. Because equals and hashCode on Path.Element is defined to use the normalized index I had to limit the cacheable path elements to the ones with an undefined index.
> Prevent excessive Path.Element instances
> ----------------------------------------
>
> Key: JCR-1715
> URL: https://issues.apache.org/jira/browse/JCR-1715
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core, jackrabbit-spi-commons
> Reporter: Marcel Reutegger
> Priority: Minor
> Attachments: JCR-1715-part1.patch, JCR-1715-part2.patch
>
>
> Even when a CachingHierarchyManager is used jackrabbit creates a lot of Path.Element instances. The internally used PathMap (spi-commons) creates new Path.Element instances whenever a path is constructed, even when the path is constructed from cached PathMap.Elements.
> Running a test with 10k nodes results in 250k Path.Element instances being created and held in memory (mostly for events).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.