Performance benchmarks and timing for event and impact management operations
This topic presents timing approximations for the following operations in an environment that includes event and impact management:
- Stop and start times for a BMC TrueSight Infrastructure Management Server
- Publish times
- Input/output operations per second for a BMC TrueSight Infrastructure Management Server and Database
- Network bandwidth utilization between the BMC TrueSight Infrastructure Management Server and the BMC Atrium CMDB Server
- Related topics
The following environment is used as a sample for the timing estimates.
Sample event management and impact management environment
Metric | Amount or value |
|---|---|
Number of CIs | 50 K |
Number of service models | 3 |
Number of levels | 6 |
Number of events per day | 400 K |
Maximum number of CIs in a service model | 20 K |
Number of impact events out of 400 K | 312 K |
Stop and start times for a BMC TrueSight Infrastructure Management Server
The following table shows the amount of time necessary to stop and start a BMC TrueSight Infrastructure Management Server in a large environment with event and impact management.
Action | Duration |
|---|---|
Stop the server | 2 min 10 sec |
Start the server | 9 minutes |
Publish times
The following table shows the amount of time it takes to publish a new service model in each environment.
Environment | Publish time |
|---|---|
Small (5 K CIs and relationships) | 32 minutes |
Medium (10 K CIs and relationships) | 39 minutes |
Large (20 K CIs and relationships) | 1 hour |
The following table shows the amount of time it takes to publish a service model in which 1,000 CIs and relationships are added, updated, or deleted. Times are measured on a large environment.
Action | Publish time |
|---|---|
Add | 16 minutes |
Update | 19 minutes |
Delete | 30 minutes |
Input/output operations per second for a BMC TrueSight Infrastructure Management Server and Database
The input/output operations per second (IOPS) in a BMC TrueSight Infrastructure Management Server networks is often measured by the number of read and write bytes per second for computer storage devices, such as the hard disk.
The following table presents hardware, software, and BMC TrueSight Infrastructure Management Server load details, and the resulting IOPS for the embedded SAP SQL Anywhere database on the BMC TrueSight Infrastructure Management Server.
Deployment details | Load details |
|---|---|
Integration Service | Self-Monitoring Service, only |
Infrastructure Management version | 9.0 |
Operating system | Red Hat Enterprise Linux Server release 6.0 (Santiago) |
Number of processors | 4 |
Memory | 32 GB |
Number of CIs | 50 K |
Number of events per day | 400 K |
The following table shows different IOPS values for the database server.
IOPS | Value |
|---|---|
I/O read operations/sec | 20 K |
I/O write operations/sec | 249624 |
I/O read bytes/sec | 16 |
I/O write bytes/sec | 224816 |
Network bandwidth utilization between the BMC TrueSight Infrastructure Management Server and the BMC Atrium CMDB Server
In BMC TrueSight Infrastructure Management Server networks, the bandwidth is often measured as the amount of data that is transferred from the Integration Service to the BMC TrueSight Infrastructure Management Server over a specified period.
The following values show the network bandwidth utilization to transfer 5,000 CIs between the BMC TrueSight Infrastructure Management Server and BMC Atrium CMDB:
- Average: 44 KB per second
- Minimum: 5 KB per second
- Maximum: 177 KB per second
Related topics
Performance-benchmarks-and-timing-for-data-and-event-management-operations
Performance-benchmarks-and-timing-for-the-BMC-Cloud-Lifecycle-Management-integration