# Coordinate map loading gets slower with more data in the data set and more visualizations on the dashboard

**URL:** <https://discuss.elastic.co/t/coordinate-map-loading-gets-slower-with-more-data-in-the-data-set-and-more-visualizations-on-the-dashboard/120757>\
**Category:** Kibana\
**Created:** [February 21, 2018, 3:13am UTC](https://discuss.elastic.co/t/coordinate-map-loading-gets-slower-with-more-data-in-the-data-set-and-more-visualizations-on-the-dashboard/120757 "2018-02-21T03:13:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbarclay](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@mbarclay](https://discuss.elastic.co/u/mbarclay)\
**Post date:** [February 21, 2018, 3:13am UTC](https://discuss.elastic.co/t/coordinate-map-loading-gets-slower-with-more-data-in-the-data-set-and-more-visualizations-on-the-dashboard/120757/1 "2018-02-21T03:13:58Z")

</div>

We’re using Elastic and Kibana 6.1.0.

I have a simple Kibana dashboard with 2 visualizations - a coordinate map and a stacked bar graph.

The map take about 4 secs to load. If I remove the bar graph from the dashboard the map loads instantly (\<1sec). If I filter the data to a smaller set, the map loads faster. If I add additional visualizations to the dashboard, loading of the map gets progressively slower.  
I have checked the response times of the ES queries and they are fast (15-50mS), so it looks like it's something internal to Kibana.

(Attached is the network trace showing the map tile loading times when I have the bar graph included on the dashboard)

 ![network_loading1](https://us1.discourse-cdn.com/elastic/original/3X/4/1/41a258f968e6065ad71548f79beac8e6935eb68f.png)

Here is the ES response - it took just 39ms:

{"responses":[{"took":39,"timed\_out":false,"\_shards":{"total":15,"successful":15,"skipped":0,"failed":0},"hits":{"total":16945,"max\_score":0.0,"hits":},"aggregations":{"filter\_agg":{"doc\_count":449,"2":{"buckets":[{"key":"r3gx22","doc\_count":219,"3":{"location":{"lat":-33.88062902726233,"lon":151.1886139959097},"count":219}},{"key":"r3grm5","doc\_count":42,"3":{"location":{"lat":-33.86477700434625,"lon":151.0441299341619},"count":42}},{"key":"r3grmc","doc\_count":35,"3":{"location":{"lat":-33.87268503662199,"lon":151.0835239570588},"count":35}},  
\<...snip...\>  
,"status":200}]}

If I add a filter to the data, the map tiles load pretty much instantly (less than 1 sec):

(Attached is the network trace showing the map tile loading times with filter added. )

 ![network_loading2](https://us1.discourse-cdn.com/elastic/original/3X/d/3/d3af9815623ff098365d5530673262cd587fe152.png)

The ES response:

{"responses":[{"took":40,"timed\_out":false,"\_shards":{"total":15,"successful":15,"skipped":0,"failed":0},"hits":{"total":10407,"max\_score":0.0,"hits":},"aggregations":{"filter\_agg":{"doc\_count":40,"2":{"buckets":[{"key":"r3gqqk","doc\_count":8,"3":{"location":{"lat":-34.03450103010982,"lon":151.10156893730164},"count":8}},{"key":"r3gqz7","doc\_count":6,"3":{"location":{"lat":-33.948447005823255,"lon":151.1391789559275},"count":6}},{"key":"r6584z","doc\_count":4,"3":{"location":{"lat":-33.70954901911318,"lon":151.29493097774684},"count":4}},{"key":"r3gx22","doc\_count":4,"3":{"location":{"lat":-33.88062902726233,"lon":151.1886139959097},"count":4}},{"key":"r3gpxn","doc\_count":3,"3":{"location":{"lat":-33.799500041641295,"lon":150.77999998815358},"count":3}},  
\<... snip ...\>  
,"status":200}]}

It appears that loading of the tiles is somehow related to either the amount of data or visualizations in the dashboard. As mentioned above, I can’t see any issue with the ES queries (they are fast!), the problem just manifests itself in the loading of the map tiles. To me, it looks like it's something internal.

The issue is compounded when more visualizations are added and can take \>20 seconds, rendering the dashboard almost unusable.

---

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [February 22, 2018, 3:27pm UTC](https://discuss.elastic.co/t/coordinate-map-loading-gets-slower-with-more-data-in-the-data-set-and-more-visualizations-on-the-dashboard/120757/2 "2018-02-22T15:27:11Z")

</div>

@thomasneirynck would you mind taking a look at this?

---

<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:** [March 13, 2018, 12:04am UTC](https://discuss.elastic.co/t/coordinate-map-loading-gets-slower-with-more-data-in-the-data-set-and-more-visualizations-on-the-dashboard/120757/3 "2018-03-13T00:04:15Z")

</div>

imho, this is likely related to a regression that is fixed here: [https://github.com/elastic/kibana/pull/15629](https://github.com/elastic/kibana/pull/15629). This is available 6.2. Can you check if this issue still persists after upgrading?

---

<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:** [April 10, 2018, 12:04am UTC](https://discuss.elastic.co/t/coordinate-map-loading-gets-slower-with-more-data-in-the-data-set-and-more-visualizations-on-the-dashboard/120757/4 "2018-04-10T00:04:19Z")

</div>

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