# Esrally loaddriver configurations

**URL:** <https://discuss.elastic.co/t/esrally-loaddriver-configurations/276803>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [June 23, 2021, 2:06pm UTC](https://discuss.elastic.co/t/esrally-loaddriver-configurations/276803 "2021-06-23T14:06:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![purushothamkdr143](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/purushothamkdr143/32/90242_2.png) [@purushothamkdr143](https://discuss.elastic.co/u/purushothamkdr143)\
**Post date:** [June 23, 2021, 2:06pm UTC](https://discuss.elastic.co/t/esrally-loaddriver-configurations/276803/1 "2021-06-23T14:06:56Z")

</div>

Hi All,

I am trying to setup esrally in k8s, As per the [Tips and Tricks — Rally 2.2.1 documentation](https://esrally.readthedocs.io/en/stable/recipes.html#distributing-the-load-test-driver) it is good approach or solution to distribute the load to loaddrivers. what would be the better configurations for loaddrivers(like cpu,ram). kindly 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:** [June 28, 2021, 9:35am UTC](https://discuss.elastic.co/t/esrally-loaddriver-configurations/276803/2 "2021-06-28T09:35:46Z")

</div>

Since you intend to use Rally in k8s, I assume you'll be using the [Rally Docker image](https://hub.docker.com/r/elastic/rally). As mentioned [in the docs](https://esrally.readthedocs.io/en/stable/docker.html#limitations) the Rally Docker image doesn't (currently at least) support distributing the load driver, so it'd be best to ensure that wherever Rally ends up running, limited resources on the load driver are not going to be a cause for bottlenecking your benchmark.

Depending on which track you use you may need to ensure there is ample amount of memory available; the standard tracks in [GitHub - elastic/rally-tracks: Track specifications for the Elasticsearch benchmarking tool Rally](https://github.com/elastic/rally-tracks) are of static nature and therefore most challenges don't require a whole lot of RAM, with the exception of challenges that simulate update workloads in which case more data needs to be held in RAM. Other tracks, like [GitHub - elastic/rally-eventdata-track: Rally track for simulating event-based data use-cases](https://github.com/elastic/rally-eventdata-track), generate data -- for indexing and querying -- dynamically and therefore require more CPU and Memory.

More concretely I'd check:

1. That the Rally container always ends up running on the same underlying host to reduce run to run variation (this is of course more pertinent to the target Elasticsearch itself, but it's good to ensure stable performance on the load driver too) and that the container doesn't end up running on a host that is severely overloaded.

2. Container and underlying host metrics while the benchmark is running to ensure that the benchmark isn't affected by CPU/Disk IO/Network/Memory bottlenecks.

---

<div class="post-metadata">

**Author:** ![purushothamkdr143](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/purushothamkdr143/32/90242_2.png) [@purushothamkdr143](https://discuss.elastic.co/u/purushothamkdr143)\
**Post date:** [July 2, 2021, 8:59am UTC](https://discuss.elastic.co/t/esrally-loaddriver-configurations/276803/3 "2021-07-02T08:59:11Z")

</div>

Thank you for the information.

---

<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:** [July 30, 2021, 8:59am UTC](https://discuss.elastic.co/t/esrally-loaddriver-configurations/276803/4 "2021-07-30T08:59:42Z")

</div>

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