Default execution order: Deleterandom after deleteseq

[abhineet99]

In the default benchmark execution order, deleterandom is executed after deleteseq. This gives very low numbers for deleterandom, which can be explained in tree-based engines by less traversal due to previous deletions. Should deleterandom/deleteseq be executed just after fillseq (anyhow db is reset before fillrandom)?
The whole idea assumes default execution order, with no --benchmarks parameter supplied.

[igchor]

Well, there is probably no one, best ordering for those benchmarks. The performance of delete (both seq and random) will probably be different depending on whether you called fillrandom or fillseq before.

I believe that you should always specify the benchmarks explicitly (run them in a specific order) - to best simulate your workload.