# Slow queries - is ES waiting for resources?

**URL:** <https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273>\
**Category:** Elasticsearch\
**Created:** [March 27, 2024, 11:27am UTC](https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273 "2024-03-27T11:27:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pgala](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pgala/32/127490_2.png) [@pgala](https://discuss.elastic.co/u/pgala)\
**Post date:** [March 27, 2024, 11:27am UTC](https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273/1 "2024-03-27T11:27:46Z")

</div>

Hello,

I run the simple query with one term filter. During the heavy indexing into ES, the search took:

- for 40 shards - 0.2s
- for 80 shards - \>10s

My elastic setup:  
Elastic 8.5  
Node: 5 x 16vCPU, 64GB

- 5 data nodes (15 vcpu, 48GB ram)
- 3 elastic-master
- 5 elastic-client

In the Kibana profiler, for both cases, every step has a similar time. The difference is in the `Cumulative time`.

In metrics I don’t observe a slow queries:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/f/4f84dec141eed812e24d7f9e466f22ae4935f25a.jpeg)

Why do we observe a slow query on 80 shards? Which metric should I use to detect problem? (I am thinking that ES is waiting for connection or thread)

Patryk.

---

<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:** [March 27, 2024, 11:39am UTC](https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273/2 "2024-03-27T11:39:26Z")

</div>

One of the most common limiting factors for Elasticsearch performance is disk I/O. What type of storage are you using? What does disk utilisation and await look like during the time the query runs?

---

<div class="post-metadata">

**Author:** ![pgala](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pgala/32/127490_2.png) [@pgala](https://discuss.elastic.co/u/pgala)\
**Post date:** [March 27, 2024, 11:48am UTC](https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273/3 "2024-03-27T11:48:22Z")

</div>

We use [Azure Premium SSD](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssds):

```auto
StorageClass: managed-csi-premium
Capacity: 3Ti

```

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/9/09c783db86b8e1247915e0fcb8f4cbfa614224b1.png)

> await look like during the time the query runs?

How can I check it?

---

<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:** [March 27, 2024, 11:56am UTC](https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273/4 "2024-03-27T11:56:28Z")

</div>

> [@pgala](#):
>
> How can I check it?

I would run `iostat -x` on one of the data nodes.

---

<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:** [April 24, 2024, 11:57am UTC](https://discuss.elastic.co/t/slow-queries-is-es-waiting-for-resources/356273/5 "2024-04-24T11:57:01Z")

</div>

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