# Disk space utilisation of an Elasticsearch Index

**URL:** <https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404>\
**Category:** Elasticsearch\
**Created:** [June 2, 2020, 8:29pm UTC](https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404 "2020-06-02T20:29:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![PRODIPTO](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@PRODIPTO](https://discuss.elastic.co/u/PRODIPTO)\
**Post date:** [June 2, 2020, 8:29pm UTC](https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404/1 "2020-06-02T20:29:17Z")

</div>

Is there a way to calculate the amount of space that an elasticsearch index will need based on the log file size and the number of fields that are being extracted from the log texts.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 2, 2020, 9:36pm UTC](https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404/2 "2020-06-02T21:36:46Z")

</div>

It's better to try by indexing few thousands of documents and you'll get a good idea.

---

<div class="post-metadata">

**Author:** ![PRODIPTO](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@PRODIPTO](https://discuss.elastic.co/u/PRODIPTO)\
**Post date:** [June 3, 2020, 9:00am UTC](https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404/3 "2020-06-03T09:00:44Z")

</div>

I am doing it that way but i just want to know if there is a way to do capacity estimation like Oracle ...

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 3, 2020, 9:24am UTC](https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404/4 "2020-06-03T09:24:50Z")

</div>

Not really because it depends on a lot of factors. One of them is the compression of the `_source` field. Another one is the mapping and the analyzers you are using for each field...

Our solution architects do have some ways based on their experience to give an estimation but there's nothing better than trying on real data.

---

<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 1, 2020, 9:24am UTC](https://discuss.elastic.co/t/disk-space-utilisation-of-an-elasticsearch-index/235404/5 "2020-07-01T09:24:54Z")

</div>

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