Chat now with support
Chat with Support

Foglight 7.1.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

Java Virtual Machine Tuning

Before you proceed with JavaTM Virtual Machine tuning, it is important to note the following:

•
Foglight® 5 is a Java application that ships with and uses the Oracle® Java Hotspot Virtual Machine (JVM). While there are other vendors of JVMs, the Oracle JVM should not be replaced or altered.
 
* 
NOTE: Quest acknowledges that under certain circumstances you may have to use a different Java Runtime Environment than either of the ones (one for the Management Server and one for the Agent Manager) bundled with Foglight. If that is the case, see the “Updating the Java Runtime Environment” section in Chapter 2 (“Best Practices”) of the Foglight Upgrade Guide.
•
Foglight is designed to run on a wide range of platforms and configurations, and is very scalable. It can be used to monitor several computers/nodes within a department and to monitor an entire enterprise with thousands of nodes.
 
* 
NOTE: Some out-of-the-box settings may not be optimal for every scenario.

This section provides information on how to tune the JVM to achieve maximum performance.

•
Getting Started
•
Foglight JVM Configuration
•
Common Symptoms and Tuning Resolutions

Getting Started

The following factors heavily impact JVM utilization:

•
the number of monitored computers/nodes
•
the number of observed metrics (such as CPU load, memory utilization, I/O throughput, and so on) for each node
•
the length of the time period for which Foglight® is configured to preserve historical data about observations
•
the granularity of the observations over that time period
•
the number of alarms in the system
•
the platform architecture (32- versus 64-bit address space)
•
the processes (services, database, Foglight Agent Managers, and so on) competing for CPU and memory

Foglight JVM Configuration

To review or modify Foglight® JVM configuration options, locate the following file:

<foglight_home>\config\server.config

Foglight reads JVM options from values of server.vm.optionsX properties, where X is a number from 0 to 99.

For example:

server.vm.option0 = "-Xms2048m";
server.vm.option1 = "-Xmx2048m";
 
* 
NOTE: After any change to server.config, you must restart the server.

The JVM options currently in effect (the default Foglight JVM options, server.config settings, and command line arguments) are all logged in the server log file during startup.

JVM Options

The following table describes the most commonly used Oracle® Hotspot JVM options:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating