# Kibana 5.2.2 GUI takes 3m 10sec to load initially

**URL:** <https://discuss.elastic.co/t/kibana-5-2-2-gui-takes-3m-10sec-to-load-initially/170057>\
**Category:** Kibana\
**Created:** [February 26, 2019, 6:50pm UTC](https://discuss.elastic.co/t/kibana-5-2-2-gui-takes-3m-10sec-to-load-initially/170057 "2019-02-26T18:50:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rbendik](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rbendik](https://discuss.elastic.co/u/rbendik)\
**Post date:** [February 26, 2019, 6:50pm UTC](https://discuss.elastic.co/t/kibana-5-2-2-gui-takes-3m-10sec-to-load-initially/170057/1 "2019-02-26T18:50:17Z")

</div>

Hi all,

Yes I know Im on an old version 😛

I have been living with Kibana taking 3 mins and 10 seconds to load initially for as long as I have inherited this current system. We capture huge amount of metrics so I didnt really give this a second thought, nor do i have a proper testing environment, until recently.

First page that loads is the discover app: \_/app/kibana#/discover?_g=()_

`kibana.defaultAppId: "discover"`

I now have a temp test environment where I have less than 24hrs worth of data, and Kibana still takes 3+mins to load! I timed it with my live env and the initial load time is the same.

I found this: [Kibana 5.2 UI takes a very long time to load](https://discuss.elastic.co/t/kibana-5-2-ui-takes-a-very-long-time-to-load/74447/2) but **a)** dont have stats button and **b)** dont have any load balancing configs

I am not an expert user, can anyone advise how I could possibly speed the loading time and or resolve this?

Please let me know what info I can provide (and how to get it) needed for you to help me.

I have two servers: 4x CPU, 32GB RAM, 150GB local disk

**\_cat/nodes?v**

```
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
192.168.1.152 26 74 1 0.29 0.29 0.33 d - host2
192.168.1.151 15 69 1 0.27 0.39 0.45 md * host1

```

**\_cluster/health?pretty**

```
cluster_name	"es_sandbox"
status	"green"
timed_out	false
number_of_nodes	2
number_of_data_nodes	2
active_primary_shards	26
active_shards	52
relocating_shards	0
initializing_shards	0
unassigned_shards	0
delayed_unassigned_shards	0
number_of_pending_tasks	0
number_of_in_flight_fetch	0
task_max_waiting_in_queue_millis	0
active_shards_percent_as_number	100

```

**\_cat/shards/log-\*?v&pretty**

```
index shard prirep state docs store ip node
log-2019.02.26 2 p STARTED 118087 139.9mb 192.168.1.151 host1
log-2019.02.26 2 r STARTED 118087 140.6mb 192.168.1.152 host2
log-2019.02.26 1 r STARTED 118443 140mb 192.168.1.151 host1
log-2019.02.26 1 p STARTED 118443 123.9mb 192.168.1.152 host2
log-2019.02.26 3 r STARTED 117958 140.4mb 192.168.1.151 host1
log-2019.02.26 3 p STARTED 117958 139.8mb 192.168.1.152 host2
log-2019.02.26 4 p STARTED 118144 112.3mb 192.168.1.151 host1
log-2019.02.26 4 r STARTED 118144 140.6mb 192.168.1.152 host2
log-2019.02.26 0 r STARTED 118149 123.8mb 192.168.1.151 host1
log-2019.02.26 0 p STARTED 118149 123.9mb 192.168.1.152 host2

```

**\_cat/indices/log-\*?v&s=index**

```
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open log-2019.02.26 UEbj2K8LQMyjM9MF4fybiQ 5 1 592191 0 1.3gb 669mb

```

**\_cat/indices?v**

```
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open healthmonitoring-app1-2019.02.26 KdoEeIKJRLa-x8WUp7mJlw 5 1 195 0 1mb 511.6kb
green open healthmonitoring-app2-2019.02.26 lXlyqtM0Qv2vkwtKK9t41Q 5 1 154 0 705.9kb 356.6kb
green open transactionlogging-app2-2019.02.26 y_ISZkAAQVOgA0j-_90uCA 5 1 3309 0 4.4mb 2.2mb
green open log-2019.02.26 UEbj2K8LQMyjM9MF4fybiQ 5 1 604817 0 1.3gb 681.4mb
green open transactionlogging-app1-2019.02.26 uKIZRbfoQNa3giB0ds09IQ 5 1 2857 0 4mb 2mb
green open .kibana -t_CtgkdTKm22AbX79uuIQ 1 1 4 0 55.6kb 27.8kb

```

thanks in advance!

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [February 27, 2019, 4:20pm UTC](https://discuss.elastic.co/t/kibana-5-2-2-gui-takes-3m-10sec-to-load-initially/170057/2 "2019-02-27T16:20:48Z")

</div>

@rbendik

are you talking about Kibana showing the little spinning-icon for a long time until you see the page, or are you talking about after the Discover page opens up, how long it takes for the chart and the table to appear?

---

<div class="post-metadata">

**Author:** ![rbendik](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rbendik](https://discuss.elastic.co/u/rbendik)\
**Post date:** [February 28, 2019, 6:07am UTC](https://discuss.elastic.co/t/kibana-5-2-2-gui-takes-3m-10sec-to-load-initially/170057/3 "2019-02-28T06:07:06Z")

</div>

Hi Thomas,

I have it set so that when Kibana loads for the first time, its automatically set to start the 'discover' app (hope thats the right terminology).

First page that loads is the discover app: \_/app/kibana#/discover? _g=()_

`kibana.defaultAppId: "discover"`

Once that that page loads for the first time the after 3 mins, user experience seems normal.

Last night I played around with upgrading one of our instances and upgraded from 5.2.2 ---\> 5.6.0 and now the Discover page opens in a few seconds. I think I remember seeing a blog somewhere that stated that earlier versions of Kibana had a bug loading data initially.

I thought one of my configs was off. If its not a bug and you know a fix please let me know. thanks!

---

<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:** [March 28, 2019, 6:07am UTC](https://discuss.elastic.co/t/kibana-5-2-2-gui-takes-3m-10sec-to-load-initially/170057/4 "2019-03-28T06:07:08Z")

</div>

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