Performance benchmarks and tuning for Infrastructure Management

Follow the performance and scalability recommendations for your type of deployment. You can deploy Infrastructure Management to collect performance data, collect external events, manage service models, or any combination of these functions.

• When an Infrastructure Management deployment includes data collection and event management, the BMC TrueSight Infrastructure Management Server manages performance data from BMC PATROL Agents, and manages external events from the BMC Event Adapter and BMC PATROL Agents.
• When a Infrastructure Management deployment includes event and impact management, the BMC TrueSight Infrastructure Management Server manages external events from the BMC Event Adapter, and manages impact data from service models.

For performance guidelines and tuning recommendations, consult the following topics:

• Frequently asked questions (FAQ) about performance and scalability
• Best practices and configuration guidelines for performance and scalability
• Tuning a data collection and event management deployment
• Tuning the Infrastructure Management database for performance
• Performance benchmarks and tuning for a PATROL Agent
• Tuning best practices for BMC Remedy AR System to support large service models

Variables that affect performance and scalability

The performance of a BMC TrueSight Infrastructure Management Server depends on several variables, and the performance and scalability guidelines and recommendations address these. Substantial changes in any of the following variables can change the expected scaling and performance numbers:

• Total number of monitor instances. A Monitored Instance is the equivalent of the NT_CPU BMC PATROL application class.

• Total number of attributes. An attribute in Infrastructure Management corresponds to the CPUutilisation parameter in BMC PATROL.
• Service model content, including the following considerations:
  • Number of service models
  • Number of configuration items (CIs) per service model
  • Depth of a service model
• Types of monitored devices
• Number of key performance indicators (KPIs)
• Retention period of data and events
• Number of adapters and monitors on each Integration Service
• Number of concurrent users
• Number of external events per day
• Number of alarms and abnormalities per day
• Disk I/O of the database server
• Network bandwidth utilization
• Hardware configuration, including the number of CPUs, amount of memory, and storage technology (such as SAN or RAID)