# Performance of a Saved Search 'table view' in Dashboard severely worse than Discover

**URL:** <https://discuss.elastic.co/t/performance-of-a-saved-search-table-view-in-dashboard-severely-worse-than-discover/90169>\
**Category:** Kibana\
**Created:** [June 20, 2017, 10:47pm UTC](https://discuss.elastic.co/t/performance-of-a-saved-search-table-view-in-dashboard-severely-worse-than-discover/90169 "2017-06-20T22:47:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![poorbob](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@poorbob](https://discuss.elastic.co/u/poorbob)\
**Post date:** [June 20, 2017, 10:47pm UTC](https://discuss.elastic.co/t/performance-of-a-saved-search-table-view-in-dashboard-severely-worse-than-discover/90169/1 "2017-06-20T22:47:25Z")

</div>

Forgive me if I missed something online or in the documentation, but I can't seem to figure out why a saved search would perform so differently in the 'Disocver' tab as opposed to the 'Dashboard' tab.

In the Dev Tools debugger, I was seeing \<= **20 ms** response times for a relatively simple query:  
{"bool":{"filter":{"term":{"hostname":"xxxx"}}}}

This same query in the 'Discover' view for 'Week to day' takes around **600 ms**. This in it of itself perplexed me a bit, but it seems to be API overhead (correct me if I'm wrong please 🙂 ).

A dashboard with only one visualization, this same saved search, and the _exact same_ time range, yields a far worse result. Averaging **4600 ms**.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [June 21, 2017, 10:48pm UTC](https://discuss.elastic.co/t/performance-of-a-saved-search-table-view-in-dashboard-severely-worse-than-discover/90169/2 "2017-06-21T22:48:41Z")

</div>

I'm not sure why the response time would be different. The `_msearch` API is used in both places.

Is there possibly different sorting of fields in the different areas? That could have to do with the difference.

You can look at the raw request for the searches using the Spy panel, and then send the queries to ES to see if ES is handling it differently.

---

<div class="post-metadata">

**Author:** ![poorbob](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@poorbob](https://discuss.elastic.co/u/poorbob)\
**Post date:** [June 22, 2017, 12:05am UTC](https://discuss.elastic.co/t/performance-of-a-saved-search-table-view-in-dashboard-severely-worse-than-discover/90169/3 "2017-06-22T00:05:14Z")

</div>

I noticed it was the same `_msearch` API which is what confused me the most.

Thanks for pushing me to look at the request body! (although I could not find this 'Spy panel' in Kibana 5, I used chrome dev tools)

Anyways, my issue is resolved. It appears the dashboard view was injecting a `query_string` body that really bogged down the response time. By changing `"highlightAll": true` to `"highlightAll: false` in the saved search object it now matches the speed of the Discover view.

---

<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:** [July 20, 2017, 12:05am UTC](https://discuss.elastic.co/t/performance-of-a-saved-search-table-view-in-dashboard-severely-worse-than-discover/90169/4 "2017-07-20T00:05:36Z")

</div>

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