サポートと今すぐチャット
サポートとのチャット

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

Appendix: Performance Health Check

The purpose of a health check is to quickly ensure that Foglight® is functioning properly. There are many things you can check. The more important ones are documented in this chapter.

Is the Server Getting the Right Amount of Memory?

By default, Foglight® tries to reserve three quarters of the local available physical memory. It is normal for Foglight to consume all of that memory on start up. Foglight reserves its full amount of memory on start up. Foglight is configured this way to avoid excess garbage collection.

Foglight uses a lot of temporary memory. This is due to the metric processing. It is normal and healthy for Foglight’s internal memory consumption to rise and fall.

If there is enough memory reserved, the Foglight JavaTM Virtual Machine (JVM) heap graph will display an adequate amount of free memory. It is normal for the memory to cycle up and down. As long as these memory cycles are not close together (which indicates excessive garbage collection), then all is well. Also, as long as free memory continues to be returned through garbage collection, then the amount of memory configured is fine.

Management Server Memory is Healthy if ...

Management Server Memory Checks

Check the -Xmx and -Xms settings in the Foglight® log to make sure they match expectations.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択