# Index Settings for Optimizing Indexing Throughput

**URL:** <https://discuss.elastic.co/t/index-settings-for-optimizing-indexing-throughput/178323>\
**Category:** Elasticsearch\
**Created:** [April 24, 2019, 8:04pm UTC](https://discuss.elastic.co/t/index-settings-for-optimizing-indexing-throughput/178323 "2019-04-24T20:04:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [April 24, 2019, 8:04pm UTC](https://discuss.elastic.co/t/index-settings-for-optimizing-indexing-throughput/178323/1 "2019-04-24T20:04:41Z")

</div>

Hi,  
In our logging clusters we're indexing at around 40k msg/sec and 500gb per index per day. The storage backend is ceph and sometimes it struggles as load increases over time etc.

Consequently, I'm toying wondering what I might do to optimize indexing in a way that accounts for sub-optimal storage. One of those things I'm considering is to double the size of `index.translog.flush_threshold_size`. Is this considered a good move when looking to maximise throughput? We're already have `index.refresh_interval` set to 30s so I figured making this change could align reasonably well with that...

Regards,  
D

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [April 25, 2019, 6:17am UTC](https://discuss.elastic.co/t/index-settings-for-optimizing-indexing-throughput/178323/3 "2019-04-25T06:17:48Z")

</div>

> [@dawiro](#):
>
> One of those things I'm considering is to double the size of `index.translog.flush_threshold_size` . Is this considered a good move when looking to maximise throughput?

I'm not sure it'll make much difference, but you can try.

Looking at the manual page on [tuning for indexing speed](https://www.elastic.co/guide/en/elasticsearch/reference/7.0/tune-for-indexing-speed.html) the advice to avoid network-attached storage stands out. Could you move to a [hot/warm architecture](https://www.elastic.co/blog/hot-warm-architecture-in-elasticsearch-5-x)? This would allow you to index to fast local disks and then move today's indices into your Ceph cluster once indexing is complete.

---

<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:** [May 23, 2019, 6:17am UTC](https://discuss.elastic.co/t/index-settings-for-optimizing-indexing-throughput/178323/4 "2019-05-23T06:17:55Z")

</div>

Closed on May 23, 2019, 6:17am UTC

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