Poor Dashlet Performance 1.4B
-
SeanFromIT
- Posts: 105
- Joined: Sun Dec 12, 2010 9:07 pm
Poor Dashlet Performance 1.4B
In Chrome 9 (Linux and Windows), the processing wait after clicking the blue Add to Dashboard icon is so long (>1min) that Chrome thinks the page has gone unresponsive and prompts you to kill it. If you wait long enough, it eventually comes back and works. Is there any way to improve dashlet performance?
Re: Poor Dashlet Performance 1.4B
Does this happen with specific dashlets or all of them?
Can you try a different browser and see if the same time delays are present?
Can you try a different browser and see if the same time delays are present?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Ethan Galstad
President
Ethan Galstad
President
-
SeanFromIT
- Posts: 105
- Joined: Sun Dec 12, 2010 9:07 pm
Re: Poor Dashlet Performance 1.4B
Dashlets I tried include all of them on the tactical overview page (services/hosts/network overview/etc). Rebooting the nagiosxi server seemed to improve performance slightly. I imported the nagiosxi VM as-is (512MB RAM, 1CPU). Do you recommend increasing its resources? If so, what are the recommended VM system specs?
Re: Poor Dashlet Performance 1.4B
How many checks do you have running on your server? (hosts+services).
Performance can differ quite a bit based on what you're monitoring and if you're using active vs passive checks, etc. However, I would generally recommend 1gig of RAM at the minimum for a production server. The more browser windows are open the more AJAX requests will be made to the server, decreasing your performance.
There's a new page in the Admin menu, called Performance Settings. This page lets you tweak some things in the interface to increase your performance. Using the "unified" pages will take away your ability to make everything into a dashlet, but it will increase performance a great deal, as well as decreasing the frequency of AJAX requests for the dashlets.
Performance can differ quite a bit based on what you're monitoring and if you're using active vs passive checks, etc. However, I would generally recommend 1gig of RAM at the minimum for a production server. The more browser windows are open the more AJAX requests will be made to the server, decreasing your performance.
There's a new page in the Admin menu, called Performance Settings. This page lets you tweak some things in the interface to increase your performance. Using the "unified" pages will take away your ability to make everything into a dashlet, but it will increase performance a great deal, as well as decreasing the frequency of AJAX requests for the dashlets.