...

All tests involved creating a single object node container resource with one or more descendant nodesresources.  Versioning had three modes: enabled on all test objects containers (TRUE), disabled on all test objects containers (FALSE), or enabled on the root object container and on half of the children (HALF).  onParentVersion was set to either VERSION or COPY (for non-versioned tests this has no effect).  Scaling was tested by increasing the number of descendants (100, 1000) and by increasing the size of the jcr:content property on the descendant (roughly 10kb vs 1mb).  Three types of descendant nodes resources were tested: auto-named children nodes resources with auto-generated intermediate folders (child), named children nodes resources (named), and datastreams binaries (DS).

After all the descendants were created and assigned the versionable mixin, when appropriate, a single new version of the root node resource was created (New Version Time).  Total time spent creating descendants and enabling versioning on them is recorded as Total Child Creation Time.

Time to create a new version of the root

...

resource

The creation of a new version of the root node resource was only a small portion of the overall time spent in setting up each test (~1.6% mean, 7.6% max), although there was a significant increase in the amount of time required when auto-named children were used as the descendants.  Generally, using COPY mode resulted in a slower new version creation times than VERSION.

...

https://docs.google.com/spreadsheets/d/1SnFE-mUMEJnFUr3hXvg8UVBhnl4pq05lDTGlGR_VwYw

Multiple versions of the same

...

container

Created a single node resource with one datastream binary and then created new versions of the noderesource:

Performance drop-off was considerably faster when numerous datastreams binaries (1000) were added to the root node resource prior to creating many new versions of the noderesource.

Data

https://docs.google.com/spreadsheets/d/1QRieqQTq4LtR5r5AU0LpUPO7_C_ieBNGKU1ezqSrG5M

...