Best practices for performance tuning
Use these best practice guidelines to help configure
your Tivoli Netcool/OMNIbus system
for optimal performance. Work through each of the steps in turn to
help you identify and resolve changes that adversely affect performance,
and to fine tune performance.
- Run the ObjectServer with profiling enabled
Use profiling to measure the amount of time spent running SQL queries on the ObjectServer and to identify which client connections are using up excessive resources. - Collect statistical information about triggers
Timing information about triggers, including the number of times the trigger has been raised and the number of times the trigger has fired, are saved to the catalog.trigger_stats table. - Review and revise your system architecture
Use the multitiered customizations provided with Tivoli Netcool/OMNIbus to deploy your installation in a one-, two-, or three-tiered architecture, in which the components sit within collection, aggregation, and display layers. - Enable the stats_triggers trigger group
In the default ObjectServer configuration, the stats_triggers group uses triggers to gather several statistics and metrics. You can enable the trigger group in a production environment. - Review and revise your probe configuration files
Carefully review the probe properties file and rules file settings to ensure that neither introduce any inefficiency to incoming event processing. - Configure event flood detection
Configure your probes to detect when they are subject to an event flood or other anomalous event rates, and to perform remedial actions. - Manage the volume of information in the alerts.details table
When a high volume of alert information is stored in the alerts.details table, ObjectServer performance significantly deteriorates. - Use a monitoring agent to monitor and manage Tivoli Netcool/OMNIbus resources
An IBM Tivoli Monitoring agent is available for monitoring Tivoli Netcool/OMNIbus health and performance, automation triggers, and event activity and distribution. This monitoring agent includes a set of automations that add further instrumentation to the ObjectServer. - Review and amend your SQL queries, and create a selection of well-designed, efficient indexes
It is useful to understand how SQL queries are optimized so that you can construct efficient SQL queries. Review your existing SQL queries and amend them to benefit from optimization and indexing. - Track the performance trends at regular intervals
As time progresses, various factors could affect the performance of the ObjectServer. Establish a performance baseline and periodically monitor performance to compare the metrics against those collected previously. Investigate significant differences above or below the baseline and fine tune as required.
Parent topic: Performance tuning