# ILM Performance in search

**URL:** <https://discuss.elastic.co/t/ilm-performance-in-search/307951>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [June 23, 2022, 7:07am UTC](https://discuss.elastic.co/t/ilm-performance-in-search/307951 "2022-06-23T07:07:40Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [June 23, 2022, 8:53am UTC](https://discuss.elastic.co/t/ilm-performance-in-search/307951/4 "2022-06-23T08:53:24Z")

</div>

Have a look at [this thread](https://discuss.elastic.co/t/data-stream-with-hot-warm-cold-tiers-read-performance/307192).

In older versions this was indeed an issue and Kibana has over the years implemented a few different workarounds. In recent versions this is however no longer considered an issue and all indices belonging to the pattern are queried.

---

_[View the full topic](https://discuss.elastic.co/t/ilm-performance-in-search/307951)._