立即与支持人员聊天
与支持团队交流

Foglight 5.9.7 - 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

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.

Possible Actions

•
Tune the database cache parameters. You may need to allocate more memory to the database if I/O utilization is high.
•
Move the database to a more powerful machine.
•
Tune the database optimization.
•
Run the following commands to check the database timing metrics:
•
./fglcmd.sh  -usr foglight -pwd foglight -cmd util:topologyexport  -f handlers.xml -topology_query CatalystPersistenceHandler
•
./fglcmd.sh  -usr foglight -pwd foglight -cmd util:metricexport -f retrieve-last-n-values-time.csv -metric_query "retrieveLastNValuesTime from CatalystPersistenceHandler for 1 week" -output_format csv
•
./fglcmd.sh  -usr foglight -pwd foglight -cmd util:metricexport -f retrieve-time.csv -metric_query "retrieveTime from CatalystPersistenceHandler for 1 week" -output_format csv
•
./fglcmd.sh  -usr foglight -pwd foglight -cmd util:metricexport -f retrieve-earliest-time.csv -metric_query "retrieveEarliestTimeTime from CatalystPersistenceHandler for 1 week" -output_format csv
•
The metrics returned in the CSV file are in milliseconds. Look for times of 500 or greater in AVERAGE, or greater than 10000 in MAX. If these values are consistently high, the database is failing to keep up with the load, causing the Management Server to be slow.

Is the Database Growth Reasonable?

Database growth is a long term concern, but it should be assessed early. Foglight controls database growth with persistence policies that determine how data is rolled up.

A health check on database growth is really about making sure that you have a database size expectation. This can be done using the Foglight® sizing spreadsheet. Once a size is determined, it can be configured into Foglight’s self-monitoring rules to ensure that adequate warning is provided.

Without a purge policy in place, Foglight will grow indefinitely. By default, Foglight is not equipped with a purge policy.

Database Growth is Healthy if ...

•
You have a target maximum for how large you will allow your database to get.
•
You have appropriate policies in place to keep the database smaller than that maximum.
•
The database growth patterns indicate proper growth rate.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级