# Kibana taking time to load discover

**URL:** <https://discuss.elastic.co/t/kibana-taking-time-to-load-discover/192204>\
**Category:** Kibana\
**Created:** [July 25, 2019, 9:00am UTC](https://discuss.elastic.co/t/kibana-taking-time-to-load-discover/192204 "2019-07-25T09:00:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrashid](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@mrashid](https://discuss.elastic.co/u/mrashid)\
**Post date:** [July 25, 2019, 9:00am UTC](https://discuss.elastic.co/t/kibana-taking-time-to-load-discover/192204/1 "2019-07-25T09:00:09Z")

</div>

I have around 6 GB of data coming to elastic search per day.  
The problem is that it takes around 5-6 seconds to load discover or conduct any search. I was trying to tune - to make it faster.

I have the following observations :

1. I have enabled the default shard and replica allocation. That is , 5 shards and 1 replica per index. But because I am using one node , the replica is not assigned and hence health of the index is yellow. I can also see that i have 5 unassigned shards. Can this slow down the discover ? The shards are already unassigned , how can it consume resource ?

2. I don't want to disable the highlight of search.

3. Also the default **discover:sampleSize** has been reduced to just 100.

4. I have around 83 saved searches.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/0/206c0c85300f3fae30ebef07494b1aeb85bd079c.png)

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [July 25, 2019, 1:03pm UTC](https://discuss.elastic.co/t/kibana-taking-time-to-load-discover/192204/2 "2019-07-25T13:03:36Z")

</div>

Hi @mrashid,  
have you took a look at this: [https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) this will for sure help you on tuning your elasticsearch together with [https://www.elastic.co/guide/en/elasticsearch/reference/master/tune-for-search-speed.html](https://www.elastic.co/guide/en/elasticsearch/reference/master/tune-for-search-speed.html)

---

<div class="post-metadata">

**Author:** ![mrashid](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@mrashid](https://discuss.elastic.co/u/mrashid)\
**Post date:** [July 25, 2019, 7:35pm UTC](https://discuss.elastic.co/t/kibana-taking-time-to-load-discover/192204/3 "2019-07-25T19:35:41Z")

</div>

Thanks @markov00 for responding back.

I have done most of the things mentioned already. I have increased the jvm heap to 30Gb from the default of 1 Gb for elastic search (as can be seen in the above scrrenshot). Have got around 15 fields only. If the shards have been unassigned , I dont need to worry that the extra shards are consuming more resources , I guess .

I have a field which I am sorting for each search query . I suspect this is taking up the time. Let me pre-index and sort it through template as mentioned one of the article. I will update here .

---

<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:** [August 22, 2019, 7:35pm UTC](https://discuss.elastic.co/t/kibana-taking-time-to-load-discover/192204/4 "2019-08-22T19:35:44Z")

</div>

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