# ES 6.8.2 Search slow when response payload \> 1 MB

**URL:** <https://discuss.elastic.co/t/es-6-8-2-search-slow-when-response-payload-1-mb/200899>\
**Category:** Elasticsearch\
**Created:** [September 24, 2019, 2:58pm UTC](https://discuss.elastic.co/t/es-6-8-2-search-slow-when-response-payload-1-mb/200899 "2019-09-24T14:58:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Javier\_Luque](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javier_luque/32/47285_2.png) [@Javier\_Luque](https://discuss.elastic.co/u/Javier_Luque)\
**Post date:** [September 24, 2019, 2:58pm UTC](https://discuss.elastic.co/t/es-6-8-2-search-slow-when-response-payload-1-mb/200899/1 "2019-09-24T14:58:58Z")

</div>

Hi everyone, I was wondering if anyone has encountered this error.

Upgraded from 6.5.2 to 6.8.2 and noticed our queries were running slow.

Using insomnia to test Elasticsearch I was running some queries and noticed that when the response content was \> 1MB, the query would take about 5s.

I reduced the fields using

`"_source": { "excludes": ["campaigns", "suggestor"] },`

to significantly reduce the payload and now my queries take about 237ms.

I'm on AWS using a T3.small server.

This is probably a misconfiguration somewhere as nothing else has changed. Is there something blatantly obvious that I'm missing.

Thanks

---

<div class="post-metadata">

**Author:** ![Javier\_Luque](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javier_luque/32/47285_2.png) [@Javier\_Luque](https://discuss.elastic.co/u/Javier_Luque)\
**Post date:** [September 24, 2019, 3:00pm UTC](https://discuss.elastic.co/t/es-6-8-2-search-slow-when-response-payload-1-mb/200899/2 "2019-09-24T15:00:51Z")

</div>

I'd like to mention that that exact same query on the 6.5.2 ES cluster is about 200ms even if the response payload \> 1 MB. (2.4MB in this 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:** [September 24, 2019, 3:12pm UTC](https://discuss.elastic.co/t/es-6-8-2-search-slow-when-response-payload-1-mb/200899/3 "2019-09-24T15:12:51Z")

</div>

T3 instances have very limited CPU which means processing large queries can starve the instance if cup resources which can delay things. I would recommend using a m5 instead.

---

<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:** [October 22, 2019, 3:13pm UTC](https://discuss.elastic.co/t/es-6-8-2-search-slow-when-response-payload-1-mb/200899/4 "2019-10-22T15:13:06Z")

</div>

Closed on October 22, 2019, 3:13pm UTC

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