# Restore slow down as it progresses through more and more shards **URL:** \ **Category:** Elasticsearch\ **Created:** [September 27, 2016, 7:53am UTC](https://discuss.elastic.co/t/restore-slow-down-as-it-progresses-through-more-and-more-shards/61568 "2016-09-27T07:53:40Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![arpan](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@arpan](https://discuss.elastic.co/u/arpan)\ **Post date:** [September 27, 2016, 7:53am UTC](https://discuss.elastic.co/t/restore-slow-down-as-it-progresses-through-more-and-more-shards/61568/1 "2016-09-27T07:53:40Z")
I have a elasticsearch cluster I am restoring to in AWS on ec2 instances. Over the first 30 minutes or so of the restoration, the data throughput was over 500mbps but as the recovery was finishing through more and more shards it started slowing down. Near the end (last 10% of shards) It has slowed to under 50mbps. I noticed this when I was snapshotting as well. I would like it to progress at the same pace throughout. Is there any reason why it slows down as it nears the end? ---
**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\ **Post date:** [September 27, 2016, 8:55am UTC](https://discuss.elastic.co/t/restore-slow-down-as-it-progresses-through-more-and-more-shards/61568/2 "2016-09-27T08:55:27Z")
Where were you measuring the data throughput? On a per-node basis? On a global level? Note that snapshot/restore throttles the restore rate on a per node basis (default 40mb per second, seting `max_restore_bytes_per_sec`). ---
**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:16pm UTC](https://discuss.elastic.co/t/restore-slow-down-as-it-progresses-through-more-and-more-shards/61568/3 "2017-07-05T22:16:58Z")
Closed on July 5, 2017, 10:16pm UTC