# ILM query optimization

**URL:** <https://discuss.elastic.co/t/ilm-query-optimization/205458>\
**Category:** Elasticsearch\
**Created:** [October 28, 2019, 12:23pm UTC](https://discuss.elastic.co/t/ilm-query-optimization/205458 "2019-10-28T12:23:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![coudenysj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/coudenysj/32/23108_2.png) [@coudenysj](https://discuss.elastic.co/u/coudenysj)\
**Post date:** [October 28, 2019, 12:23pm UTC](https://discuss.elastic.co/t/ilm-query-optimization/205458/1 "2019-10-28T12:23:45Z")

</div>

Hi,

We're using ILM to enable a hot/warm/cold architecture. We ingest quite a lot of data, and try to keep them for 90 days.

Ingest is running smoothly, but I'm trying to speed up the querying.

When I run a time based query on the `filebeat-*` index, I hit all the nodes, which is quite slow.

Is the correct solution to comma separate the time based indices, and only query the indices in the range of the requested time range?

---

<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:** [November 25, 2019, 12:23pm UTC](https://discuss.elastic.co/t/ilm-query-optimization/205458/2 "2019-11-25T12:23:46Z")

</div>

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