Skip to content

Commit

Permalink
Add a note how to benchmark Elasticsearch
Browse files Browse the repository at this point in the history
With this commit we add a note that explains when to use benchmarks and
point the reader to the macrobenchmarking tool Rally for further
information.

Relates #37694
  • Loading branch information
danielmitterdorfer authored Jan 23, 2019
1 parent f54a3b5 commit 1de286b
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions TESTING.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -631,3 +631,13 @@ inside `/etc/hosts`, e.g.:
255.255.255.255 broadcasthost
::1 localhost ElasticMBP.local`
....

== Benchmarking

For changes that might affect the performance characteristics of Elasticsearch
you should also run macrobenchmarks. We maintain a macrobenchmarking tool
called https://github.com/elastic/rally[Rally]
which you can use to measure the performance impact. It comes with a set of
default benchmarks that we also
https://elasticsearch-benchmarks.elastic.co/[run every night]. To get started,
please see https://esrally.readthedocs.io/en/stable/[Rally's documentation].

0 comments on commit 1de286b

Please sign in to comment.