Add limited-traversal query on a binary tree with one supernode

[jvolmer]

This should test the performance of a traversal on a tree with a supernode where not all neighbours of the supernode are actually required in the traversal due to respective limit.
This can be used to measure the performance changes from batching traversals (https://arangodb.atlassian.net/browse/COR-7), testable on cluster with https://github.com/arangodb/arangodb/pull/22081/files and single server with arangodb/arangodb#22062.

I also refactored the already existing script for the creation of trees for better readability.

[dmitrysper]

Hi @jvolmer - we need to see whether your refactoring changes affect existing edges and subquery tests (their results to be exact) since both suites use test data created with:

      if (testParams.edges || testParams.subqueryTests) {
        initializeEdgeCollection();
      }

Could you pls run perf-simple-branch pipeline (specifying the required ArangoDB and simple-performance-test branches)

Thanks upfront :)

[dmitrysper]

Hi @jvolmer - thanks for running the performance tests from your branches.

Now that we have results it's possible to visualize them and compare to devel (or any other branch) with the following Grafana dashboards:

• Performance Gauge (executed tests only)

• Performance Gauge - tests with degradation - single server

• Performance Gauge - tests with degradation - cluster

As you can see (especially with tests executed against the cluster) - there's a number of tests that were negatively impacted by the changes and it's not only edge or subquery subsets.

Could you pls trigger another build of perf-simple-branch so that we can have more data to compare and take a closer look at the tests' results with significant disparity (if the outcome will be similar).

Thank you in advance!