[ 
https://issues.apache.org/jira/browse/SLING-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433889#comment-16433889
 ] 

Stefan Seifert commented on SLING-7577:
---------------------------------------

a better solution might be to make use of the java NIO filesystem watch 
features instead of the current implemented manual watch-by-poll code.

i tried to migrate this 1 or 2 years ago but was scared away because it seemed 
the implementation of the NIO watch features are platform dependent with 
differences between windows and unix file systems. but i did not spent a lot of 
time on further search on this.

> FS Resource Provider slow due to frequent file stat access
> ----------------------------------------------------------
>
>                 Key: SLING-7577
>                 URL: https://issues.apache.org/jira/browse/SLING-7577
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: File System Resource Provider 2.1.12
>            Reporter: Julian Sedding
>            Assignee: Julian Sedding
>            Priority: Major
>             Fix For: File System Resource Provider 2.1.14
>
>
> The file-system resource provider is relatively slow, because it frequently 
> checks for file existence, for whether a file is a directory or a file and 
> for the last modified time.
> Normally this is not an issue, but in a setup where context aware 
> configurations are used via FSRP, there are a lot of lookups for non-existing 
> resources, which are not cached in any way. In the scenario I experienced, 
> the same lookups occurred frequently during a single HTTP request and caused 
> page-rendering to take ~5s.
> To improve this, I propose to cache file stats, including non-existence of a 
> file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to