# Benchmarking ES cluster using rally

**URL:** <https://discuss.elastic.co/t/benchmarking-es-cluster-using-rally/246320>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [August 25, 2020, 4:00pm UTC](https://discuss.elastic.co/t/benchmarking-es-cluster-using-rally/246320 "2020-08-25T16:00:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nchalise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nchalise/32/130399_2.png) [@nchalise](https://discuss.elastic.co/u/nchalise)\
**Post date:** [August 25, 2020, 4:00pm UTC](https://discuss.elastic.co/t/benchmarking-es-cluster-using-rally/246320/1 "2020-08-25T16:00:39Z")

</div>

I am benchmarking ES cluster using esrally. I have created custom tracks using ES queries only search operation not indexing. There is a consistent individual query performance gap(considering **100th percentile service time** and **Max Throughput** ) between c5 and i3 instances but the difference in the overall track execution time is 1-2 minutes.  
What are the metrics I need to consider for benchmarking? Please suggest.

---

<div class="post-metadata">

**Author:** ![dliappis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dliappis/32/56174_2.png) [@dliappis](https://discuss.elastic.co/u/dliappis)\
**Post date:** [August 26, 2020, 7:00am UTC](https://discuss.elastic.co/t/benchmarking-es-cluster-using-rally/246320/2 "2020-08-26T07:00:30Z")

</div>

Hello,

Thanks for your interest in Rally.

First of all, I'd recommend to take a look at [this presentation](https://www.elastic.co/elasticon/conf/2018/sf/the-seven-deadly-sins-of-elasticsearch-benchmarking) for an overview of common pitfalls in benchmarks.

One of the things you'll find there is the notion of warm up time, so you should ensure that your the JVM, caches etc. have all warmed up sufficiently before you consider the measurement samples report worthy. (See `warmup-iterations` and `warmup-time-period` in the [docs](https://esrally.readthedocs.io/en/stable/track.html#schedule)).

You should also monitor the usage on your instance (e.g. using the USE methodology); this is also discussed in the presentation linked above. `c5` and `i3` are vastly different in CPU, Disk and network capabilities and e.g. things can differ depending on how disk setup's done.

---

<div class="post-metadata">

**Author:** ![nchalise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nchalise/32/130399_2.png) [@nchalise](https://discuss.elastic.co/u/nchalise)\
**Post date:** [August 26, 2020, 7:53am UTC](https://discuss.elastic.co/t/benchmarking-es-cluster-using-rally/246320/3 "2020-08-26T07:53:32Z")

</div>

Thanks for the response.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 23, 2020, 7:53am UTC](https://discuss.elastic.co/t/benchmarking-es-cluster-using-rally/246320/4 "2020-09-23T07:53:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.