# Best existing tracks/challenges for benchmarking read-heavy or read-mostly workloads?

**URL:** <https://discuss.elastic.co/t/best-existing-tracks-challenges-for-benchmarking-read-heavy-or-read-mostly-workloads/166380>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [January 30, 2019, 2:46pm UTC](https://discuss.elastic.co/t/best-existing-tracks-challenges-for-benchmarking-read-heavy-or-read-mostly-workloads/166380 "2019-01-30T14:46:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![khyron4eva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/khyron4eva/32/35234_2.png) [@khyron4eva](https://discuss.elastic.co/u/khyron4eva)\
**Post date:** [January 30, 2019, 2:46pm UTC](https://discuss.elastic.co/t/best-existing-tracks-challenges-for-benchmarking-read-heavy-or-read-mostly-workloads/166380/1 "2019-01-30T14:46:36Z")

</div>

Fellow Rally users,

I'm interested in benchmarking read-heavy workloads, preferably some that already exist in Rally by default. Are there any tracks or challenges that implement such a workload already?

Cheers!

---

<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:** [January 30, 2019, 6:05pm UTC](https://discuss.elastic.co/t/best-existing-tracks-challenges-for-benchmarking-read-heavy-or-read-mostly-workloads/166380/2 "2019-01-30T18:05:08Z")

</div>

Hello,

Mentioning read-heavy I presume you mean heavy while querying.

Many of the existing [tracks](https://github.com/elastic/rally-tracks) (see: [geonames](https://github.com/elastic/rally-tracks/blob/c59234cd922300f095c6f31567373586c564b703/geonames/operations/default.json#L17-L296), [nested](https://github.com/elastic/rally-tracks/blob/c59234cd922300f095c6f31567373586c564b703/nested/operations/default.json#L7-L73), [nyc\_taxis](https://github.com/elastic/rally-tracks/blob/c59234cd922300f095c6f31567373586c564b703/nyc_taxis/operations/default.json#L17-L112), [pmc](https://github.com/elastic/rally-tracks/blob/c59234cd922300f095c6f31567373586c564b703/pmc/operations/default.json#L17-L90)) have queries. You can have a look at the results from our nightly benchmark system at [https://elasticsearch-benchmarks.elastic.co](https://elasticsearch-benchmarks.elastic.co).

If you need to adjust the load that queries generate, you can always tinker with the `clients` and `target-throughput` (e.g. [here](https://github.com/elastic/rally-tracks/blob/c59234cd922300f095c6f31567373586c564b703/geonames/challenges/default.json#L50)) in the task definitions.

Cheers,  
Dimitris

---

<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:** [February 27, 2019, 6:05pm UTC](https://discuss.elastic.co/t/best-existing-tracks-challenges-for-benchmarking-read-heavy-or-read-mostly-workloads/166380/3 "2019-02-27T18:05:10Z")

</div>

Closed on February 27, 2019, 6:05pm UTC

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