# Assigning Different Data Tier to Indices on a Same Node

**URL:** <https://discuss.elastic.co/t/assigning-different-data-tier-to-indices-on-a-same-node/367054>\
**Category:** Elasticsearch\
**Created:** [September 24, 2024, 2:42pm UTC](https://discuss.elastic.co/t/assigning-different-data-tier-to-indices-on-a-same-node/367054 "2024-09-24T14:42:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kdwolf](https://avatars.discourse-cdn.com/v4/letter/k/df788c/32.png) [@kdwolf](https://discuss.elastic.co/u/kdwolf)\
**Post date:** [September 24, 2024, 2:42pm UTC](https://discuss.elastic.co/t/assigning-different-data-tier-to-indices-on-a-same-node/367054/1 "2024-09-24T14:42:54Z")

</div>

Hello, All

I understand a concept of different tiers for various types of indices (content data, Hot, Cold, etc.) but I cannot find any reference / documentation if there is a practical benefit to assign different indices a different tier on **the same node**. For example if there is a value of having _countries_ index in data content tier, _my\_old\_loggs_ index in a cold one and _my\_precious\_customer\_data_ in a Hot tier.

I created two very simple indices _countries_ and _countries\_content_ and placed the latter into the content tier ("\_tier\_performance" : "data\_content"). I populated both with a list of countries and noticed that in my case basic GET countries\_content/\_search returned the result normally 15% to 20% quicker than GET countries/\_search.

But even if my tests are correct and there is a difference, will there be any benefit of applying such a separation in production with a small number of nodes (4-5) , please?

Elasticsearch 8.15