Additionally, if you are creating child nodes, you want them to be using a non ordered structure. If you're using an ordered parent I could see it creating a significant impact after a while.
Also, indexing. If you've got indexing going on that includes what you're inserting that may have an impact as well. -- Jason On Sat, Oct 29, 2016, at 02:27 PM, Steven Walters wrote: > On Fri, Oct 28, 2016 at 11:55 PM, Christoph Thodte > <christoph.tho...@ht-solutions.de> wrote: > > Hello! > > > > What is the best and fast way to create a lot of resources in Sling? I > > import 200.000 data rows in jcr. My importer is very fast for the 30.000 > > nodes than it will be very slow down. I commit my resourceresolver ervery > > 100 resources. The committing is fine but the time for creation of the > > resource is increased very fast. After 40.000 nodes the time is around > > 20min for creation of 100 nodes. > > > > What is the problem? How can I speed up. Can anyone support or explain this? > > As datastore I use the mongodb. With tar it's slower than mongo. I use > > Sling API not the JCR Api. That's the problem? > > I've not seen any particular performance difference in the past > between using the Sling API vs the JCR API for massive data creation > like this. > > Can you elaborate a bit more on how you're organizing the data that > you're creating within Sling? > > That is, in the past there have been known performance problems with > having a large number of direct children nodes/resources under a > single parent within the JCR. > So just wondering how you're structuring the data as you're creating > it within Sling. > Without such information, it's mostly grabbing at straws to guess what > your problem may be.
