Hi Lucian,
I couldn’t run your code example out of the box. 24 hours sounds pretty alarming, though, so I have written my own example (attached). It creates 50.000 XML documents, each sized around 160 KB. It’s not as fast as I had expected, but the total runtime is around 13 minutes, and it only slow down a little when adding more documents...
10000: 125279.45 ms 20000: 128244.23 ms 30000: 130499.9 ms 40000: 132286.05 ms 50000: 134814.82 ms
Maybe you could compare the code with yours, and we can find out what causes the delay?
Best, Christian
On Tue, Jan 10, 2017 at 4:44 PM, Bularca, Lucian Lucian.Bularca@mueller.de wrote:
Hi Dirk,
of course, querying millions of data entries on a single database rise problems. This is equally problematic for all databases, not only for the BaseX DB and certain storing strategies will be mandatory at production time.
The actual problem is, that adding 50.000 of 160 KB xml stuctures took 24 hours because that inexplicable monotonic increase of the insert operation durations.
I'll really appreciate if someone can explain this behaviour or a counterexample can demonstrate, that the cause of this behaviour is test case but not DB inherent.
Regards, Lucian