# Size of an index

**URL:** <https://discuss.elastic.co/t/size-of-an-index/330387>\
**Category:** Elasticsearch\
**Created:** [April 20, 2023, 10:48am UTC](https://discuss.elastic.co/t/size-of-an-index/330387 "2023-04-20T10:48:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchwithme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchwithme/32/137075_2.png) [@searchwithme](https://discuss.elastic.co/u/searchwithme)\
**Post date:** [April 20, 2023, 10:48am UTC](https://discuss.elastic.co/t/size-of-an-index/330387/1 "2023-04-20T10:48:27Z")

</div>

I have 9 tenants. Each tenant is about 1 TB. Could I create 1 index for each tenant? so 9 indices in total?  
this would mean each index is 1 TB  
9 TB of data over 9 indices. To maintain safe shard size, my index will have 48 Primaries (so each shard is 25 GB).

Does this design look good?

---

<div class="post-metadata">

**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:** [April 20, 2023, 11:15pm UTC](https://discuss.elastic.co/t/size-of-an-index/330387/2 "2023-04-20T23:15:23Z")

</div>

That seems reasonable.

It might be worth trying different shard sizes as from 30-50 gig is the usual recommendation, and you might find a different size is better for your use case.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 21, 2023, 4:55am UTC](https://discuss.elastic.co/t/size-of-an-index/330387/3 "2023-04-21T04:55:13Z")

</div>

The ideal shard size will depend on your data as well as your queries and latency requirements. 25GB sounds like a good starting point but i would recommend running a benchmark with realistic data and queries. The result could be larger or smaller than 25GB.

The 30GB to 50GB is often recommended for time-series data queried through aggregations. If your use case is a search use case your optimum may however be quite different.

---

<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:** [May 19, 2023, 4:55am UTC](https://discuss.elastic.co/t/size-of-an-index/330387/4 "2023-05-19T04:55:48Z")

</div>

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