We test the following configurations (all with Security and TLS enabled):
bare: Elasticsearch on an unencrypted drive
ear: Elasticsearch on a drive that is encrypted with dm-crypt to benchmark the performance impact of encryption-at-rest.
docker: Official Elasticsearch Docker image
Starting with Elasticsearch 7.7.0, benchmarks are run with the JDK that is bundled with Elasticsearch.
All benchmarks are run by Rally against the Elasticsearch master branch as of that date. The benchmark uses four bare-metal server-class machines. On one we run the benchmark driver (Rally), on the other three the benchmark candidate (one to three Elasticsearch nodes, one per machine). All machines are connected via a dedicated 10 GBit switched network.
The benchmarks are intentionally not scalability benchmarks but rather show the performance characteristics of Elasticsearch ranging from one node to at most three nodes and are mainly intended to help the development team spot performance regressions.
Benchmarks run on ephemeral AWS environments using 3x c6gd.8xlarge instances as dedicated master nodes and 6x m6gd.4xlarge instances for the hot tier. Don't use those numbers to compare with other benchmarks! Indeed:
We run nightly Graviton2 benchmarks using the m6gd.metal AWS instance type. Don't use those numbers to compare x86 vs. ARM performance! Indeed:
All other benchmarks are run on bare-metal machines with the following specifications:
All machines are connected via a dedicated 10 GBit switched network.