# Kibana dashboard slow to load because of max connections limit (http 1.1)

**URL:** <https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244>\
**Category:** Kibana\
**Created:** [September 11, 2016, 9:08pm UTC](https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244 "2016-09-11T21:08:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kartiku](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kartiku/32/11844_2.png) [@kartiku](https://discuss.elastic.co/u/kartiku)\
**Post date:** [September 11, 2016, 9:08pm UTC](https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244/1 "2016-09-11T21:08:30Z")

</div>

I have a kibana dashboard that has a large number of panels. When the page is loaded, all the panels result in queries being fired to the elasticsearch cluster. But it is very slow to load. What i noticed is that once 6 queries have been fired, all other queries are blocked/waiting to fire.

Once the result for one of the queries comes back, then another one is fired. Some of these queries are expensive, resulting in some long waiting times.

It will obviously be much better if most of the queries can be fired in parallel.

I am thinking of setting up a nginx proxy server with http 2.0. Kibana will connect to this and the proxy will pass on the request to the elasticsearch cluster.

Will this help? Is there any other approach? I am thinking of the proxy solution because nginx also allows for other conveniences like re-directing to https, caching on proxy, load balancing etc.

---

<div class="post-metadata">

**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:** [September 11, 2016, 10:18pm UTC](https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244/2 "2016-09-11T22:18:04Z")

</div>

How do you know you are hitting a connection limit?

---

<div class="post-metadata">

**Author:** ![kartiku](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kartiku/32/11844_2.png) [@kartiku](https://discuss.elastic.co/u/kartiku)\
**Post date:** [September 11, 2016, 10:35pm UTC](https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244/3 "2016-09-11T22:35:20Z")

</div>

I determined that through the networking tab on the debugging console. Are you saying this is not an issue, or is a mis-diagnosis on my part?

---

<div class="post-metadata">

**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:** [September 11, 2016, 10:36pm UTC](https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244/4 "2016-09-11T22:36:16Z")

</div>

No, I was asking how you determined this to be the problem, cause it wasn't in the post itself 🙂

---

<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 6, 2017, 1:39pm UTC](https://discuss.elastic.co/t/kibana-dashboard-slow-to-load-because-of-max-connections-limit-http-1-1/60244/5 "2017-07-06T13:39:09Z")

</div>

Closed on July 6, 2017, 1:39pm UTC