[
https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237723#comment-14237723
]
Bertrand Delacretaz commented on SLING-4216:
--------------------------------------------
This sounds like a good idea but you'll need to clarify the strategy used to
free space in the cache (delete least recently used entries?) as well as what
happens when you have a cache miss.
Note also http://sling.apache.org/documentation/bundles/caching-services.html -
if this requires cache management logic it would be good to make that logic
reusable.
> 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)
