RE: File system resource provider - Performance

>-Original Message- >From: Roy Teeuwen [mailto:r...@teeuwen.be] >Sent: Friday, September 29, 2017 4:01 PM >To: users@sling.apache.org >Cc: Stefan Seifert >Subject: Re: File system resource provider - Performance > >Hey Carsten, > >What about doing t

Re: File system resource provider - Performance

Hey Carsten, What about doing the initial scanning also async? As in that you do the initial scanning in the first scheduled run, without throwing change events for that first run Greets, Roy > On 29 Sep 2017, at 15:57, Carsten Ziegeler wrote: > > > > > Stefan

Re: File system resource provider - Performance

Hey Stefan, I was planning to give that a try too, could you maybe elaborate on what hick-ups you noticed on the different OSes? Greets Roy > On 29 Sep 2017, at 15:52, Stefan Seifert wrote: > > >> I think we could try using newer file features from Java 7 which might

Re: File system resource provider - Performance

  Stefan Seifert wrote > >> 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. > > you mean with e.g. this? > https://docs.oracle.com/javase/7/docs/api/java/nio/file/WatchService.html > > i had this on my todo

RE: File system resource provider - Performance

>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. you mean with e.g. this? https://docs.oracle.com/javase/7/docs/api/java/nio/file/WatchService.html i had this on my todo list some time ago for fsresource - but

Re: File system resource provider - Performance

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