# Comparing disk usage on ES with different configurations

**URL:** <https://discuss.elastic.co/t/comparing-disk-usage-on-es-with-different-configurations/341655>\
**Category:** Elasticsearch\
**Created:** [August 25, 2023, 7:15am UTC](https://discuss.elastic.co/t/comparing-disk-usage-on-es-with-different-configurations/341655 "2023-08-25T07:15:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hjazz6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hjazz6/32/79007_2.png) [@hjazz6](https://discuss.elastic.co/u/hjazz6)\
**Post date:** [August 25, 2023, 7:15am UTC](https://discuss.elastic.co/t/comparing-disk-usage-on-es-with-different-configurations/341655/1 "2023-08-25T07:15:30Z")

</div>

Hi,

I'm trying to optimize the disk usage on my Elasticsearch (version 8.8), and I want to see how much disk space was used (saved) after configuring different things, e.g. dynamic vs static mapping, default compression vs best\_compression, before and after running shrink/force merge API.

I was thinking I could start with an index where data was ingested using default settings, then for each of the different configurations, I would first create an index template for the destination index, then reindex the original index to the destination index. In that way, I could see how much disk space was used in the destination index vs the original index.

Is this the right way to go?

Thank you.

---

<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:** [September 22, 2023, 7:16am UTC](https://discuss.elastic.co/t/comparing-disk-usage-on-es-with-different-configurations/341655/2 "2023-09-22T07:16:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.