# Merging and indices.store.throttle.max\_bytes\_per\_sec **URL:** \ **Category:** Elasticsearch\ **Created:** [October 30, 2017, 10:31am UTC](https://discuss.elastic.co/t/merging-and-indices-store-throttle-max-bytes-per-sec/105741 "2017-10-30T10:31:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Deb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deb/32/46162_2.png) [@Deb](https://discuss.elastic.co/u/Deb)\ **Post date:** [October 30, 2017, 10:31am UTC](https://discuss.elastic.co/t/merging-and-indices-store-throttle-max-bytes-per-sec/105741/1 "2017-10-30T10:31:02Z")
Cross posting from [stackoverflow](https://stackoverflow.com/questions/47013602/significance-of-merging-and-indices-store-throttle-max-bytes-per-sec) I have gone through this [link](https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html#segments-and-merging) It is not clear to me what does `indices.store.throttle.max_bytes_per_sec` actually do? Is it like in one second if segments that are getting merged are having size more than 20 MB then it will throttle the indexing request? Can someone also explain me how does increasing the value of `max_bytes_per_sec` effects disk i/o? It appears to me increasing the value will lead to more disk I/O as now more segments can be merged ? Is it correct? Can someone let me know when does merge process kicks in? Is it like when the number of segments greater than `x` then merge process starts? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 27, 2017, 10:31am UTC](https://discuss.elastic.co/t/merging-and-indices-store-throttle-max-bytes-per-sec/105741/2 "2017-11-27T10:31:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.