Chat now with support
Chat with Support

Foglight 5.9.1 - 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 Appendix: Performance Health Check Appendix: Analyzing a Support Bundle

Possible Actions

•
Remove other processes from the system.
•
Reconfigure the virtual image to have access to more resources.
•
Move Foglight to a more powerful machine.
•
Configure the operating system to allow Foglight™ to have access to all available CPUs.

Is the Database too Slow?

A slow database slows down database queries. This in turn slows down metric queries from the browser interface.

The Database is Healthy if ...

•
The number of JDBC connections available is close to the maximum. This means that queries are not getting stuck waiting for the database to return.
•
The CPU utilization on the database machine is substantial, but not greater than 90 percent on average, indicating a non-blocked system that has enough resources available.
•
The browser interface is performing well on metric queries. This can be tested with any dashboard that graphs a metric.

Database Checks

•
First, perform the Hosts dashboard performance test from the CPU section of the health check. Poor browser interface performance coupled with low CPU utilization indicates either a server block or a database problem. To check to see if there is a database problem, proceed to the next check.
•
Check the available JDBC connections.
•
Check CPU and I/O utilization on the database machine.
•
Check the amount of memory allocated to the database:
•
On an Oracle® database, check the SGA size:
SELECT SUM(bytes) FROM v$sgainfo WHERE resizeable = ‘Yes’
•
On a MySQL database, check the InnoDB buffer pool size:
SHOW VARIABLES LIKE ‘innodb_buffer_pool_size’
•
Check the database timing metrics.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating