# Refresh latency **URL:** \ **Category:** Elasticsearch\ **Created:** [October 5, 2017, 3:46pm UTC](https://discuss.elastic.co/t/refresh-latency/102866 "2017-10-05T15:46:44Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![manast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manast/32/13705_2.png) [@manast](https://discuss.elastic.co/u/manast)\ **Post date:** [October 5, 2017, 3:46pm UTC](https://discuss.elastic.co/t/refresh-latency/102866/1 "2017-10-05T15:46:45Z")
We are experiencing significant latency in the refresh operation. In some cases refresh takes up to one minute to complete. Our index is about 150GB large and has 32 shards spread across 12 nodes. The refresh interval is currently set to 15s. My questions: - Would a lower refresh interval speed up refresh at the cost of lower indexing speed? - Would more nodes help to increase refresh performance? - Are there any other measures to be done for increasing refresh performance? Thanks, Michail ---
**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:** [October 6, 2017, 1:28am UTC](https://discuss.elastic.co/t/refresh-latency/102866/2 "2017-10-06T01:28:41Z")
> [@manast](#): > > Would a lower refresh interval speed up refresh at the cost of lower indexing speed? > Would more nodes help to increase refresh performance? Possibly, to both. What version are you on? What sort of infrastructure? ---
**Author:** ![manast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manast/32/13705_2.png) [@manast](https://discuss.elastic.co/u/manast)\ **Post date:** [October 6, 2017, 8:25am UTC](https://discuss.elastic.co/t/refresh-latency/102866/3 "2017-10-06T08:25:18Z")
We are using Elasticsearch 2.2.0. We have 12 data nodes and 3 master nodes. The data nodes have 24 GB RAM and 300 GB SSD capacity each. ---
**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:** [October 6, 2017, 8:23pm UTC](https://discuss.elastic.co/t/refresh-latency/102866/4 "2017-10-06T20:23:49Z")
What OS, what IO scheduler? ---
**Author:** ![manast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manast/32/13705_2.png) [@manast](https://discuss.elastic.co/u/manast)\ **Post date:** [October 8, 2017, 1:09pm UTC](https://discuss.elastic.co/t/refresh-latency/102866/5 "2017-10-08T13:09:43Z")
We have CentOS 7.3.1611 with the deadline scheduler ---
**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:** [October 8, 2017, 11:03pm UTC](https://discuss.elastic.co/t/refresh-latency/102866/6 "2017-10-08T23:03:54Z")
Try the noop scheduler and see if that helps. ---
**Author:** ![manast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manast/32/13705_2.png) [@manast](https://discuss.elastic.co/u/manast)\ **Post date:** [October 11, 2017, 6:36pm UTC](https://discuss.elastic.co/t/refresh-latency/102866/7 "2017-10-11T18:36:22Z")
It turns out that we don't have only SSDs. Our cluster is connected to various types of NAS including flash, SSDs and HDDs. Do you think that the NOOP scheduler would still help? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 8, 2017, 6:36pm UTC](https://discuss.elastic.co/t/refresh-latency/102866/8 "2017-11-08T18:36:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.