Chat now with support
Chat mit Support

Foglight 6.3.0 - Performance Tuning Field Guide

Overview Hardware and Operating System Tuning Management Server Tuning Java Virtual Machine Tuning Backend Database Tuning High Availability (HA) Tuning Agent Tuning Store and Forward Processing Appendix: Performance Health Check Appendix: Analyzing a Support Bundle

Possible Actions

•
If the memory utilization is consistently greater than 80 percent:
•
Allocate more memory to Foglight by increasing the value of the –Xmx configuration parameter, if the environment has enough available physical memory to support the increase.
•
Reduce the load on the server.
•
If the system is paging, reduce the amount of memory allocated to Foglight by decreasing the value of the –Xmx configuration parameter.

Is the Server Getting Enough CPU?

The server may be starved for CPU on the system hosting the Management Server. When this happens, it is typically because Foglight® is competing for CPU with other processes.

Management Server CPU is Healthy if ...

•
The Foglight® browser interface performance is fine.
•
The Management Server is the top CPU-consuming process on the system.
•
The CPU consumption does not average over 90 percent.

Management Server CPU Checks

•
After you log in for the first time and the Hosts page is drawn for the first time, test the performance of the Hosts dashboard. If it takes longer than 20 seconds for the Hosts dashboard to be drawn, then it is possible there is a CPU issue. Continue to the next check.
•
Check to see if Foglight® is consuming the bulk of the CPU on the system. If other processes are consuming CPU, then these processes should be moved to another system. Foglight needs the CPU.
•
If there are items in the run queue, Foglight may be competing for resources with another process. Check the top CPU consumers to make sure the Management Server is getting the CPU it needs.
•
If Foglight is consuming in excess of 90 percent of the CPU on average, then it needs a stronger CPU or the server needs to be tuned to do less.
•
Make sure that Foglight is consuming on all available CPUs. If it is not, a process or processor affinity setting may need to be tweaked.
•
If Foglight is not consuming significant CPU, then it is likely there is a database issue or some other performance deadlock.
•
If Foglight is running on a virtual image, it is possible that the image configuration is not providing enough resources (that is, if the browser interface is slow, you are not doing a lot of GCs, and there does not seem to be any swapping). If the CPU utilization is not 100 percent, the Management Server is not underpowered. In this scenario, if you see a run queue as well, but you do not see other processes competing, then it is likely that your ESX® configuration is not providing enough CPU.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen