# Benchmarking cluster with rally **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [July 23, 2021, 12:15pm UTC](https://discuss.elastic.co/t/benchmarking-cluster-with-rally/279475 "2021-07-23T12:15:43Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Abdelhalim](https://avatars.discourse-cdn.com/v4/letter/a/838e76/32.png) [@Abdelhalim](https://discuss.elastic.co/u/Abdelhalim)\ **Post date:** [July 23, 2021, 12:15pm UTC](https://discuss.elastic.co/t/benchmarking-cluster-with-rally/279475/1 "2021-07-23T12:15:43Z")
Hello, I have set a development cluster with 3 master Nodes, 2 hot data nodes and 1 warm node, and I wanted to benchmark it to reproduce results which looks like the results got in here : [Benchmarking and sizing your Elasticsearch cluster for logs and metrics | Elastic Blog](https://www.elastic.co/fr/blog/benchmarking-and-sizing-your-elasticsearch-cluster-for-logs-and-metrics) so I tried to benchmark with this command : ```auto esrally race --track=metricbeat --target-hosts=10.13.81.11:9200,10.13.81.12:9200,10.13.81.13:9200,10.13.81.21:9200,10.13.81.22:9200,10.13.81.23:9200 --pipeline=benchmark-only --client-options='use_ssl:true,verify_cert:true,ca_certs:'ca.crt',client_cert:'beat.crt',client_key:'beat.key',basic_auth_user:'elastic',basic_auth_password:'MyPassword'' --track-params='number_of_shards:1' --track-params='number_of_replicas:0' ``` I tested 3 times, with 1 shard, 2 shard and 3 shard. and I always have the same result of the mean Throughput which equal to : 14.9K/s I also tested in one node with the command : ```auto esrally race --distribution-version=7.13.0 --track=metricbeat ``` and i got 11K/s Could you tell me please why I am not seeing a big difference ? and what I am doing wrong if it's not the expected result as I think Best regards ---
**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:** [July 26, 2021, 5:00pm UTC](https://discuss.elastic.co/t/benchmarking-cluster-with-rally/279475/2 "2021-07-26T17:00:54Z")
Assuming that shard settings got applied correctly here are a few thoughts. The workload that you've chosen (`metricbeat`) is [quite small and very compressible](https://github.com/elastic/rally-tracks/blob/e7fa3f9ae1f77535e30896d257bae3f4a6d78227/metricbeat/track.json#L15-L21). What was the duration of your benchmark? It's very likely it was very short. For evaluating indexing throughput, you probably want to use something that resembles more the workload that you are after and is larger. You can e.g. the `http_logs` track for something more logs oriented, `pmc` if you are after large docs or `nyc_taxis` for a rather large corpora. For most tracks there are README pages describing the workload e.g. [rally-tracks/http\_logs at master · elastic/rally-tracks · GitHub](https://github.com/elastic/rally-tracks/tree/master/http_logs) You could also be having a bottleneck elsewhere, e.g. on your loaddriver, or elsewhere. I recommend taking a systematic approach ensuring that you are running valid benchmarks and detecting where the bottleneck is; there is a great tutorial linked in the [Rally docs page](https://esrally.readthedocs.io/en/stable/faq.html#what-do-latency-and-service-time-mean-and-how-do-they-relate-to-the-took-field-that-elasticsearch-returns) that you can find here: [The Seven Deadly Sins of Elasticsearch Benchmarking | Elastic](https://www.elastic.co/elasticon/conf/2018/sf/the-seven-deadly-sins-of-elasticsearch-benchmarking) or here: [Benchmarking Elasticsearch with Rally by Daniel Mitterdorfer | Search Meetup Munich - YouTube](https://www.youtube.com/watch?v=HriBY2zoChw&t=2154s) ---
**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:** [July 26, 2021, 5:09pm UTC](https://discuss.elastic.co/t/benchmarking-cluster-with-rally/279475/3 "2021-07-26T17:09:37Z")
With all the caveats mentioned in the [previous comment](https://discuss.elastic.co/t/benchmarking-cluster-with-rally/279475/2) (small workload etc.) out of curiosity I tried the `metricbeat` track against: 1. 1-node environment, `number_of_shards:0`: `26863 docs/s` 2. 3-node environment, `number_of_shards:5`: `39887.4 docs/s` and as expected got higher indexing throughput on the 3-node env. So I'd definitely look at bottlenecks and issues with your benchmarking methodology. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 23, 2021, 5:09pm UTC](https://discuss.elastic.co/t/benchmarking-cluster-with-rally/279475/4 "2021-08-23T17:09:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.