# Disable \_msearch for dashboard?

**URL:** <https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085>\
**Category:** Kibana\
**Created:** [February 14, 2017, 5:34pm UTC](https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085 "2017-02-14T17:34:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [February 14, 2017, 5:34pm UTC](https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085/1 "2017-02-14T17:34:53Z")

</div>

ES 2.4 - Kibana 4

I am running Kibana for a quite big web site (30millions event per day), using Kibana to display some aggregations, but dashboard with 5 widgets crash all the time (the msearch query get elastic error, I think about not enough memory).

We are running 3 data nodes, 2 http nodes, with 15 Go RAM each, no problem to run aggregation one by one, but msearch not.

So, I am asking if it's possible to disable msearch stuff and have widget running the query separately ?

Thanks you,

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [February 15, 2017, 6:14am UTC](https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085/2 "2017-02-15T06:14:19Z")

</div>

With a \_msearch request your giving up a small amount of time in exchange for the compounding latency of multiple \_search requests. In almost all scenarios this is preferred and there is not currently a way to natively disable the use of \_msearch. If you are having some of the queries timing out I would suggest looking into the performance of the Elasticsearch cluster itself.

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [February 15, 2017, 8:40am UTC](https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085/3 "2017-02-15T08:40:42Z")

</div>

ok got it, the response size is 50Mo !!! Woa, this is because Kibana loads all pages in one shot 😕 and we have big documents (2 discover widgets in dashboard, was causing the huge response size).

I am thinking the dashboard like a web page, I cannot imaging a web page loading ALL resources (CSS/JS/IMG) in one time, isnit (or via HTTP/2.0) ?

Also, load widget separately could help for caching, or even to load other data source (yeah!).

Thanks you,

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [February 15, 2017, 9:53am UTC](https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085/4 "2017-02-15T09:53:34Z")

</div>

Hmm

I am not 100% sure, but Kibana is using gzip with elasticsearch ?

---

<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:** [March 15, 2017, 9:54am UTC](https://discuss.elastic.co/t/disable--msearch-for-dashboard/75085/5 "2017-03-15T09:54:23Z")

</div>

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