[
https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246481#comment-14246481
]
Carsten Ziegeler commented on SLING-4216:
-----------------------------------------
Wrt skipping, not sure how expensive BloomFilterUtils.probablyContains is, but
this call could be skipped if everything is cached, in addition, getting the
vanity paths if mapEntries is null could be skipped as well for this case, so
if everything is cached a simple
mapEntries = this.resolveMapsMap.get(vanityPath);
should be enough
> Limit the number of vanityPath MapEntry
> ----------------------------------------
>
> Key: SLING-4216
> URL: https://issues.apache.org/jira/browse/SLING-4216
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
> Attachments: SLING-4216-patch.txt
>
>
> At the moment there isn't any limit to the number of MapEntry that are cached
> in memory.
> If the number of vanityPaths/alias is extremely high this can cause OOM.
> It would be good to have a way to limit the amount of memory used by the
> MapEntry cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
