You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Jörg Hoh (JIRA)" <ji...@apache.org> on 2017/10/03 20:15:00 UTC

[jira] [Resolved] (SLING-7154) SlingServletResolver should use a LRU map to cache resolved servlets

     [ https://issues.apache.org/jira/browse/SLING-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörg Hoh resolved SLING-7154.
-----------------------------
    Resolution: Duplicate

Duplicate to SLING-6635 (raised by myself ....)

> SlingServletResolver should use a LRU map to cache resolved servlets
> --------------------------------------------------------------------
>
>                 Key: SLING-7154
>                 URL: https://issues.apache.org/jira/browse/SLING-7154
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.4.14
>            Reporter: Jörg Hoh
>
> The ServletResolver currently uses a simple Map to hold the resolved servlets; when reached the cache is full, it does not purge old/unused entries, but just warns (once!), and then silently bypasses the cache and resolves the script again.
> It should rather use a LRU cache to hold recently resolved servlets, which makes it possible to adapt to the current workload instead of being stuck to the workload during the filling of the cache.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)