The script was run with default values: 10,000 children under the same parent, PUT requests.
Synthetic graph created by the benchmark script. The graph is unique for each request and consists of 200 triples which are partly random data, with a consistent size and variation:
15'45" running time 0.094" per resource 3.4M triples total in repo at the end of the process
Retrieval of parent resource (~10000 triples), pipe to /dev/null: 3.64"
Peak memory usage: 2.47Gb Database size: 3.3 Gb
25' running time 0.152" per resource
Some gaps every ~40-50 requests, probably disk flush
Retrieval of parent resource (10K triples), pipe to /dev/null: 2.13"
Peak memory usage: ~650 Mb (3 idle workers, 1 active) Database size: 523 Mb