Hi, yes, this is an odd behaviour. The whole tree is scanned on startup and this is blocking. In addition, if you have a large tree the periodic scanning for changes (this is polling) is probably not optimal either.
I think we could try using newer file features from Java 7 which might make the scanning obsolete. But I've never looked into it. Regards Carsten Roy Teeuwen wrote > Hey all, > > We are using the file system resource provider to monitor a directory to be > attached as resources. Currently in our directory we have around 5 levels > deep with in total 200.000 files. The problem we are facing is that when our > application starts up, it takes an unusual amount of time to get online. It > appears that the file system resource provider is building up the monitor > cache and this is the cause of the performance decay. We currently have one > file system resource provider config for the entire directory, would it be > better to have multiple on lower levels, and if so, how many files maximum > per resource provider config should we take? > > Or maybe the file system resource provider is not made to work on this large > amount of files? For our use-case it looks perfect because we also use the > events being triggered and because we like to use the files as resources in > our application without having to import them as actual jcr nodes. > > Greets, > Roy > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
