# Discover tab timing out with single \_msearch request

**URL:** <https://discuss.elastic.co/t/discover-tab-timing-out-with-single-msearch-request/110325>\
**Category:** Kibana\
**Created:** [December 5, 2017, 11:12am UTC](https://discuss.elastic.co/t/discover-tab-timing-out-with-single-msearch-request/110325 "2017-12-05T11:12:25Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [December 5, 2017, 12:20pm UTC](https://discuss.elastic.co/t/discover-tab-timing-out-with-single-msearch-request/110325/8 "2017-12-05T12:20:25Z")

</div>

Is that comparison based on the same size hardware being used?

When querying, is the load across you nodes balanced (if not, you may be affected by the issue [discussed in this thread](https://discuss.elastic.co/t/load-not-evenly-distributed/101343)).

As `_msearch` queries do not stream results back, I would guess either of these to have more impact on the performance issue you are seeing than the actual rendering.

---

_[View the full topic](https://discuss.elastic.co/t/discover-tab-timing-out-with-single-msearch-request/110325)._