# Dealing with slow \_msearch calls **URL:** \ **Category:** Kibana\ **Created:** [October 14, 2015, 2:24pm UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183 "2015-10-14T14:24:19Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [October 14, 2015, 2:24pm UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/1 "2015-10-14T14:24:19Z")
Hi, Kibana 4.x seems to send requests from Dashboard in a single \_msearch call. When one has a lot of data in Elasticsearch this could result in timeouts. How do others deal with this, other than increasing connection timeouts? Thanks, Otis ---
**Author:** ![Pawel\_Rog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pawel_rog/32/141223_2.png) [@Pawel\_Rog](https://discuss.elastic.co/u/Pawel_Rog)\ **Post date:** [October 14, 2015, 2:58pm UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/2 "2015-10-14T14:58:19Z")
I'm also wondering why Kibana 4 is not sending a few queries at once. Browser allows to use a few HTTP connections to a given host. This means instead of sending one big msearch it would be possible to send a few smaller ones and receive results incrementally (dashboards components loading incrementally). Maybe it is possible to configure Kibana 4 somehow and I'm missing something. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 14, 2015, 9:56pm UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/3 "2015-10-14T21:56:42Z")
This is something I (sorta) was getting at when I raised this - [https://github.com/elastic/kibana/issues/4390](https://github.com/elastic/kibana/issues/4390) But yeah, it'd be nice if it did this. ---
**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\ **Post date:** [October 24, 2015, 3:32am UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/4 "2015-10-24T03:32:27Z")
Thanks Mark. I'm going to assume other Kibana users will bring this up with time and then maybe the implementation will be changed. ## Otis Monitoring - Log Management - Alerting - Anomaly Detection Elasticsearch Consulting - Support - Training - [http://sematext.com/](http://sematext.com/) ---
**Author:** ![tangyong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tangyong/32/7375_2.png) [@tangyong](https://discuss.elastic.co/u/tangyong)\ **Post date:** [January 26, 2016, 12:11pm UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/5 "2016-01-26T12:11:29Z")
I have found that the issue is very important for large index(daily e-commerce scene...), and Whether having any plan for implementing the functionality? Thanks! --Tang ---
**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:** [September 29, 2016, 9:02am UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/6 "2016-09-29T09:02:53Z")
Haaa, I understand why my elasticsearch is down after playing with Kibana ;-( When I query each widget alone (via Sense), the duration is no more than 7ms, but from Kibana, each widget takes more than 1seconde to load data !!! Any advices about that ? Thanks you ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:37pm UTC](https://discuss.elastic.co/t/dealing-with-slow--msearch-calls/32183/7 "2017-07-06T13:37:51Z")