Performance Tweaking

Added by Matt Hughes, last edited by Eric Johnson on Dec 12, 2007  (view change)

Improving HQ's Performance

This page explains settings that can help improve the performance of the platform.

HQ Server Restart Required

The HQ Server must be restarted for the configuration changes explained on this page to take effect.

Applications whose settings can be tweaked to improve performance:

You can also improve performance by changing HQ cache settings.

If you have any comments or suggestions for this help page, please submit them at the bottom of the page by clicking Add Comment.

JBossMQ

HQ relies on JBossMQ to serve the JMS messages that power the alerting subsystem. Having many alert definitions might cause performance problems. Change these two configuration settings — in the configuration file hq-engine/server/default/deploy/jms/hsqldb-jdbc2-service.xml — to improve performance:

Configuration Setting Description Default Value Change to This Value
HighMemoryMark The message cache starts softening messages when the heap size reaches this value 50MB 80% of the -xmx setting
MaxMemoryMark The message cache becomes very aggressive when the heap reaches this value 60MB 90% of the -xmx setting

For more detail, consult JBoss's webiste.

Note that this is related to the JVM heap size, and not the size consumed by the JMS messages. So, the default settings are clearly very low. Furthermore, because the storage is actually the built-in HypersonicSQL running in-memory, we're actually incurring additional memory anyways.

back to top

Lather

Lather is HQ's own connection protocol for communication between the Agent and the Server. If your HQ deployment has over 25 Agents, you need to increase the maximum Lather connections to at least the number of Agents, ideally more. In the following code snippet, found in the file hq-engine/server/default/deploy/lather-jboss.sar/jboss-lather.war/WEB-INF/web.xml, change the 25 value to the value suited to your environment.

<init-param>
    <param-name>net.hyperic.lather.maxConns</param-name>
    <param-value>25</param-value>
</init-param>

Save the file and restart HQ.

Large values of Max Lather Connections Require More Database Connections

If the lather.maxConns value goes higher than around 60-75, you need to increase the maximum number of database connections. In the following code snippet, found in the file conf/templates/hq-ds.xml, change the 100 value to a number 1.5--2 times greater than the lather.maxConns value. to the value suited to your environment.

<max-pool-size>100</max-pool-size>

For example, for a deployment with 60 Agents, set lather.maxConns to 75 and max-pool-size to 150.

back to top

Return to Installing FUSE HQ: The Complete Guide

Labels

 
(None)