Using the project at https://github.com/futures/modeshape-baseline-test
and the JMeter test plan at https://github.com/futures/ff-jmeter-madness,
I got the following results for creating a JCR node in a modeshape installation as a baseline for fcrepo4 performance, which shows that enabling "query" in the modeshape configuration has indeed the largest impact on performance so far.
TODO: test using sync/async
modeshape-config1.json:
A modeshape configuration using a binary store of type cache, with transactions enabled, and query enabled
modeshape-config2.json:
A modeshape configuration using a binary store of type file, with transactions disabled, and query enabled
modeshape-config3.json:
A modeshape configuration using a binary store of type file, with transactions disabled, and query disabled
