# Improving Reindex Performance in v5.6

**URL:** <https://discuss.elastic.co/t/improving-reindex-performance-in-v5-6/161659>\
**Category:** Elasticsearch\
**Created:** [December 20, 2018, 10:38am UTC](https://discuss.elastic.co/t/improving-reindex-performance-in-v5-6/161659 "2018-12-20T10:38:15Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![ndtreviv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ndtreviv/32/22494_2.png) [@ndtreviv](https://discuss.elastic.co/u/ndtreviv)\
**Post date:** [December 21, 2018, 10:53am UTC](https://discuss.elastic.co/t/improving-reindex-performance-in-v5-6/161659/8 "2018-12-21T10:53:55Z")

</div>

Actually, I've just seen this: [Shards Distribution in Multiple disks](https://discuss.elastic.co/t/shards-distribution-in-multiple-disks/121489/4)

It looks from the data that the one with seemingly fewer shards from my index has more data for other miscellaneous/internal indices (created by Kibana/Monitoring etc).

That sort of makes sense. It's useful to know. In future, for example, I'd hold off on installing kibana until my indices have spread their data nicely across all the disks.

---

_[View the full topic](https://discuss.elastic.co/t/improving-reindex-performance-in-v5-6/161659)._