[
https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237909#comment-14237909
]
Antonio Sanso commented on SLING-4216:
--------------------------------------
[~cziegeler] this might also work.
IMHO though the majority of times the request are not looking for a vanityPath
resource. Hence if the bloom filter is configured correctly to not have too
many false positive the majority of times you are not hitting the search (that
with Oak should no be that expensive if an index for sling:vanityPath would
exist).
With your approach I am not also too much sure how to "solve" SLING-3290. With
the bloom filter approach solving SLING-3290 would be a nice side effect
> 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
>
> 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)
