System Performance

Configuring the System Performance Plugin

The Container Manager Reference Implementation supports the setting of a System Performance plugin. This plugin is used to obtain performance statistics about the underlying platform running Openwings. This information is used to create net.openwings.availability.PerformanceReport objects, returned from net.openwings.container.ContainerManager.getPerformanceReports().

(Note: In future releases, this information will be used by the Container Clustering implementation for load balancing.)

The choice of SystemPerformance plugin is set by the $OW_HOME/openwings-${VERSION}/policies/ContainerManagerPolicy.xml file. The value to change is right near the top of the file:

There are three system performance implementations that come with the reference implementation: one for Windows, one for Solaris/SunOS, and one for Linux.

If your platform is Windows, set the value to "com.gd.openwings.container.manager.WindowsPerformance". This implementation works for 98/NT/2000/XP.

If your platform is Linux, set the value to "com.gd.openwings.container.manager.LinuxPerformance". This implementation should work on most Linux implementations. It utilizes the following shell commands to obtain its data:

• free -kt
• ifconfig -a
• cat /proc/cpuinfo
• df -k .

If your platform is Solaris (SunOS), set the value to "com.gd.openwings.container.manager.SolarisPerformance". This implementation should work on most Unix implementations. It utilizes the following shell commands to obtain its data:

• swap -s
• ifconfig -a
• mpstat
• df -k .

The SystemPerformance plugin interface is located at net.openwings.container.utilities.PlatformPerformance, so you can easily write your own implementation.

Observing Performance Output

The Container Manager uses the System Peformance plugin to update its performance reports every few seconds. To see output of the data obtained, the "container" and "performance" status log levels must be enabled for the Container Manager. See the following link if you aren't familiar with the LogPolicy.