I use nxlog to collect Windows performance stats and store them in Elasticsearch and have a dashboard with 14 visualizations to show all different stats such as ASP.NET requests, processor time, available memory, disk read/write, etc.
There are two sources of perfmon, A includes 5 servers and B includes 18 servers. Perfmon data are stored into two ES clusters on servers with lots of CPU, RAM, and SSD. The same Kibana dashboard (via export and import) for A and B are on separate Kibana instances.
My issue is when I use Google Chrome to view the dashboard
- With perfmon dashboard for A (5 servers), the Chrome tab uses around 200MB of memory.
- With perfmon dashboard for B (18 servers), the Chrome tab uses up to 1GB of memory and is usually very slow to unusable point.
When I try to open the perfmon dashboard for B in Firefox, Firefox will hang because of unresponsive script
Script: http://server:port/bundles/kibana.bundle.js?v=9689:3698 Error: [$rootScope:inprog] $digest already in progress http://errors.angularjs.org/1.4.7/$rootScope/inprog?p0=%24digest (http://server:port/bundles/commons.bundle.js?v=9689:27679) Version: 4.4.0 Build: 9689 Error: Error: [$rootScope:inprog] $digest already in progress http://errors.angularjs.org/1.4.7/$rootScope/inprog?p0=%24digest (http://server:port/bundles/commons.bundle.js?v=9689:27679) __WEBPACK_AMD_DEFINE_RESULT__</window.onerror@http://server:port/bundles/commons.bundle.js?v=9689:63832:25
Perfmon index is pretty small, weekly index is about 1 GB. The number of documents retrieved from ES is about 12K for last 1 hour.
I also have big indexes ranging from 10 to 100 GB daily indexes and Kibana dashboards for them work fine on the same Kibana instance that I have trouble viewing the perfmon dashboard.
I wonder if anyone knows possible causes or ways to find out the causes of the issue.