Benchmarketing is a common activity for many DBMS products whether they are
closed or open source. Most products need new users to maintain viability
and marketing is part of the process. The goal for benchmarketing is to show
that A is better than B. Either by accident or on purpose good
benchmarketing results focus on the message A is better than B rather than A
is better than B in this context. Note that the context can be critical and
includes the hardware, workload, whether both systems were properly
configured and some attempt to explain why one system was faster.
He’s very right about every aspect in the post.
Maybe the only small edit I’d make would be to emphasize once more that the context is critical and if left out it’ll invalidate the value of the benchmark.
Original title and link: Benchmark(et)ing