# Kibana very slow

**URL:** <https://discuss.elastic.co/t/kibana-very-slow/90157>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [June 20, 2017, 8:32pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157 "2017-06-20T20:32:46Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![iremmats](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iremmats/32/55316_2.png) [@iremmats](https://discuss.elastic.co/u/iremmats)\
**Post date:** [June 20, 2017, 8:32pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/1 "2017-06-20T20:32:46Z")

</div>

Hi,

So one of the main issues during the Betas was that the Kibana node was limited to 1GB memory and therefore was very slow. Now with the GA of ECE we can choose whatever size we want for Kibana.

Still its super slow. I assume we are doing something wrong on our end. The installation guide has been followed, the machines are under quite easy load etc.

It takes about 10 seconds for the discover window in Kibana to load when there are a few thousand documents to show.

What can I do to find the reason and/or fix this?

---

<div class="post-metadata">

**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\
**Post date:** [June 20, 2017, 8:45pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/2 "2017-06-20T20:45:16Z")

</div>

Hi @iremmats

What is the new memory cap for Kibana now?

---

<div class="post-metadata">

**Author:** ![iremmats](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iremmats/32/55316_2.png) [@iremmats](https://discuss.elastic.co/u/iremmats)\
**Post date:** [June 20, 2017, 8:46pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/3 "2017-06-20T20:46:05Z")

</div>

The instance we are looking at right now we have at 4GB.

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [June 20, 2017, 9:03pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/4 "2017-06-20T21:03:57Z")

</div>

Do your documents have a large number of fields? You might be running into this bug: [https://github.com/elastic/kibana/issues/12131](https://github.com/elastic/kibana/issues/12131)

You could check your browser's dev tools to see if the Elasticsearch query is taking a long time (as would be the case with the bug above).

---

<div class="post-metadata">

**Author:** ![iremmats](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iremmats/32/55316_2.png) [@iremmats](https://discuss.elastic.co/u/iremmats)\
**Post date:** [June 20, 2017, 9:18pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/5 "2017-06-20T21:18:27Z")

</div>

In the cluster im looking at now we have one index with 300 documents and total of 54 fields. To open the Visualize window in Kibana takes 2.5 seconds according to dev tools.

The other index has 600k documents, takes 25 seconds to open. It has much more fields though.

If I remove the index pattern for the larger index and try to add it again, the screen that tries to load all fields keeps on trying to load forever.

---

<div class="post-metadata">

**Author:** ![iremmats](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iremmats/32/55316_2.png) [@iremmats](https://discuss.elastic.co/u/iremmats)\
**Post date:** [June 20, 2017, 9:25pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/6 "2017-06-20T21:25:51Z")

</div>

The bigger index has 2500 fields and its doing fine in our 2.3.3 cluster.

---

<div class="post-metadata">

**Author:** ![iremmats](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iremmats/32/55316_2.png) [@iremmats](https://discuss.elastic.co/u/iremmats)\
**Post date:** [June 20, 2017, 9:26pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/7 "2017-06-20T21:26:45Z")

</div>

If I query Level:\* instead of \* in Kibana its much quicker.

---

<div class="post-metadata">

**Author:** ![iremmats](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iremmats/32/55316_2.png) [@iremmats](https://discuss.elastic.co/u/iremmats)\
**Post date:** [June 20, 2017, 9:37pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/8 "2017-06-20T21:37:15Z")

</div>

Setting doc\_table:highlight:all\_fields to false in Kibana makes things quick again.  
Any good explanation why its still fast in 2.3.3? 🙂

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [June 20, 2017, 10:02pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/9 "2017-06-20T22:02:54Z")

</div>

I think there are a couple of things at play here. We made some changes to improve the accuracy of highlighting in 5.3 which may be contributing to the slowdown. But as you noted, a query like `<field>:*` will be faster than `*`. This is [because of the new all fields mode](https://github.com/elastic/kibana/issues/12097). I suspect it's the combination of the two that's really hurting us. Both of these issues are on our roadmap to fix.

---

<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 4, 2017, 10:02pm UTC](https://discuss.elastic.co/t/kibana-very-slow/90157/10 "2017-07-04T22:02:55Z")

</div>

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