You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/06/17 12:32:09 UTC

[jira] Updated: (SLING-1010) Add cache to speed up resolution of missing JCR resources

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

Jukka Zitting updated SLING-1010:
---------------------------------

    Attachment: MissingPathCache.patch

Attached the proposed patch (against bundles/jcr/resource).

Note that I haven't yet run too many performance tests to justify this cache. I have a very specific use case where the effect is quite noticeable, but I'm not yet sure how well this works in general (it's a source of some extra lock contention, there may be observation and memory overheads that I'm overlooking, etc.). The cache also only works properly if the installation only accesses a single workspace and no namespace remappings are used.

Due to these concerns the cache is disabled by default and there's a configuration option for enabling it if needed.

> Add cache to speed up resolution of missing JCR resources
> ---------------------------------------------------------
>
>                 Key: SLING-1010
>                 URL: https://issues.apache.org/jira/browse/SLING-1010
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR Resource
>            Reporter: Jukka Zitting
>            Priority: Minor
>         Attachments: MissingPathCache.patch
>
>
> As recently discussed [1], I'm trying to speed up resolution of resources that don't exist. The resource resolution algorithm in Sling is very powerful, but it also needs to look at many different paths when a particular resource does not exist.
> I've implemented a simple cache that is designed to work around this performance issue until the speed of such negative repository path lookups has improved.
> [1] http://markmail.org/message/wlamd7xvagaexmzu

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.