# Kibana dashboard slowelness

**URL:** <https://discuss.elastic.co/t/kibana-dashboard-slowelness/165971>\
**Category:** Elasticsearch\
**Created:** [January 28, 2019, 9:46am UTC](https://discuss.elastic.co/t/kibana-dashboard-slowelness/165971 "2019-01-28T09:46:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![aboullaite](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@aboullaite](https://discuss.elastic.co/u/aboullaite)\
**Post date:** [January 28, 2019, 9:46am UTC](https://discuss.elastic.co/t/kibana-dashboard-slowelness/165971/1 "2019-01-28T09:46:47Z")

</div>

Hi,

Recently we start noticing that kibana request takes very long to show up (around +30s)!

 ![59%20AM](https://us1.discourse-cdn.com/elastic/original/3X/6/3/636f911e53eb7e11f9c07b6f9b5f3a648b8d88e1.png)  
I believe this is not related to kibana, since it does nothing except sending`_msearch` requests to our elasticsearch cluster (correct me if I'm wrong)!

Our elasticsearch cluster is composed of 3 data nodes + 1 load balancer! each data node machine is 32 Go of RAM and 32 vCPU! We've been monitoring the 3 nodes lately and no peak in cpu usage, network communication issue or high memory consumption, everything seems normal.

We reached around 7000+ indices, each of one shard and 1 replica, each is ~7Mo of size. Could the many indices be the issues ? should we run a clean up process to remove old indices ?

Thanks

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 28, 2019, 9:57am UTC](https://discuss.elastic.co/t/kibana-dashboard-slowelness/165971/2 "2019-01-28T09:57:18Z")

</div>

> [@aboullaite](#):
>
> We reached around 7000+ indices, each of one shard and 1 replica, each is ~7Mo of size. Could the many indices be the issues ? should we run a clean up process to remove old indices ?

Yes, that is quite likely as that sounds like far too many shards and indices for a cluster that size. Having lot of small indices and shards [can be very inefficient and cause performance issues](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster).

---

<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:** [February 25, 2019, 9:57am UTC](https://discuss.elastic.co/t/kibana-dashboard-slowelness/165971/3 "2019-02-25T09:57:32Z")

</div>

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