Hi Eugene, There are 2 aspects here: The repository definitely should not take such a long time for startup (or presumably read all/many children of root at startup). But the reason why this was not seen before pertains to your second question: It is definitely not advised to store that many document anywhere in the repo, let alone root. The preferred way to use the repo is by having some kind of hierarchy that puts the documents into different folders. This allows for access control on these folders. It also allows humans a more manageable way to browse the documents. If there is on apparent hierarchy one can introduce an artificial one like day/month of creation or a hash of a property of the document, etc.
HTH Michael On 23/02/17 19:11, "Eugene Prystupa" <[email protected]> wrote: >Can anyone confirm if this is a viable storage option? We have an >Oak-backed repository with ~100,000 documents in it (and growing), and all >documents are stored as children nodes of the root node. > >We are seeing severe delays on start-up (20 minutes+) when repository is >created (new Jcr(oak).createRepository()). At appears that for whatever >reason Oak is trying to read all direct root children on start-up and that >takes a lot of time. Is storing documents not directly under root a better >choice? > >-- >Thanks, >Eugene
