# Tiny dataset very high read rate, how to optimise?

**URL:** <https://discuss.elastic.co/t/tiny-dataset-very-high-read-rate-how-to-optimise/208135>\
**Category:** Elasticsearch\
**Created:** [November 15, 2019, 9:11pm UTC](https://discuss.elastic.co/t/tiny-dataset-very-high-read-rate-how-to-optimise/208135 "2019-11-15T21:11:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sutty100](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@sutty100](https://discuss.elastic.co/u/sutty100)\
**Post date:** [November 15, 2019, 9:11pm UTC](https://discuss.elastic.co/t/tiny-dataset-very-high-read-rate-how-to-optimise/208135/1 "2019-11-15T21:11:18Z")

</div>

We are trying to work out how to improve the throughput of our elasticSearch cluster and I think our use case is a little different from normal hence my post! Our cluster is currently 3 nodes with 8GB of memory each. Our index size is really small ~50,000 documents 200MB in total size.

We deal with quite a large number of requests to the cluster e.g. 400 requests a second but this can spike to upwards of 700 at which point the cluster tends to fall over. Our monitoring shows a search time of 5ms however the CPU simply maxes out once we approach 700 requests per second.

My questions are:

Is it unreasonable to expect this cluster to handle 700 requests per second?

What would be the best shard and replica configuration? I can fairly confidently say the current config is wrong! 5 shards and a single replica.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 15, 2019, 9:46pm UTC](https://discuss.elastic.co/t/tiny-dataset-very-high-read-rate-how-to-optimise/208135/2 "2019-11-15T21:46:28Z")

</div>

With that little data I would recommend a single primary shard and two replica shards. If you are not updating the data set I would also recommend forcemerging it down to a single segment.

---

<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:** [December 13, 2019, 9:46pm UTC](https://discuss.elastic.co/t/tiny-dataset-very-high-read-rate-how-to-optimise/208135/3 "2019-12-13T21:46:29Z")

</div>

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