# Reducing Disk IO

**URL:** <https://discuss.elastic.co/t/reducing-disk-io/54923>\
**Category:** Elasticsearch\
**Created:** [July 7, 2016, 9:07am UTC](https://discuss.elastic.co/t/reducing-disk-io/54923 "2016-07-07T09:07:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dihpierrick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dihpierrick/32/40980_2.png) [@dihpierrick](https://discuss.elastic.co/u/dihpierrick)\
**Post date:** [July 7, 2016, 9:07am UTC](https://discuss.elastic.co/t/reducing-disk-io/54923/1 "2016-07-07T09:07:15Z")

</div>

Hello,

I have a ELK stack working right now. It receives around 80 docs per seconds from Logstah.  
My monitoring tool graphs the number of operations per second made on the disk.  
Here is what I get, around 35-40 operations/s :

![](https://us1.discourse-cdn.com/elastic/original/2X/1/12b4f3805370912a955196520c9be838e0505a3c.png)

What do you think of the purple graph (write operations) ? Does it look like a normal behavior ?  
What are the options, in Logstash or Elasticsearch, that can reduce the number of operations ?

I found the option index.refresh\_interval but I'm not sure if it could help.

Thank in advance for your help

Regards

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 7, 2016, 10:47pm UTC](https://discuss.elastic.co/t/reducing-disk-io/54923/2 "2016-07-07T22:47:43Z")

</div>

Why does it matter? What problem are you trying to solve?

---

<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 5, 2017, 10:37pm UTC](https://discuss.elastic.co/t/reducing-disk-io/54923/3 "2017-07-05T22:37:15Z")

</div>