Performance testing summary

General observations and anomalies

BMC BladeLogic Server Automation

• The BMC BladeLogic Server Automation server CPU usage was observed as ~ 50 percent during Compliance job executions. This was observed irrespective of the number of target servers.
• On average, the Java process for BMC BladeLogic Server Automation application server consumed around 278 percent to 300 percent out of 400 percent while running the Compliance job for target servers. This behavior was consistent throughout the scenarios, irrespective of the number of target servers.

BMC Atrium Orchestrator

• BMC Atrium Orchestrator passed for 8000 targets — that is, BMC Atrium Orchestrator successfully parsed the BladeLogic export log file of ~30 MB (CSV) in 16 hours, 58 seconds and hence could create 1 percent (80) change requests in BMC Remedy ITSM.
• CPU used by the BMC Atrium Orchestrator server during Compliance job execution was high. It consumed between 130 – 200 percent (out of 400 percent) of total physical CPU and, at peak times, it consumed almost 200 percent (out of 400 percent) of the total physical CPU. This was observed irrespective of the number of target servers.
• During the parsing of the BladeLogic export job log, maximum CPU consumed was 200 percent out of 400 percent, whereas it remained steadily around 150 – 200 percent during the parsing activity. Each core of the CPU was pegged consistently at 35 percent (four cores are available for the BMC Atrium Orchestrator server.)
• BMC Atrium Orchestrator CPU consumption spiked up when it received the SNMP trap from BladeLogic and the file adapter stored the intermediate BladeLogic compliance export log in its temporary directory.
• The BMC Atrium Orchestrator CPU activity dropped to 71 percent system CPU (out of 100 percent) when a logon request to BMC Remedy ITSM was sent.

BMC Remedy AR System

• The CPU consumption for the BMC Remedy AR System server was consistent and averaged around 5 – 7 percent. It spiked to 12 percent only in between when searches for change requests were made manually.
• The memory consumption also remained normal.

General observations about the solution

• BMC Atrium Orchestrator and BMC BladeLogic Server Automation resource utilization remains consistent across all executions.
• Resource utilization on both BMC Atrium Orchestrator and BMC BladeLogic Server Automation is not impacted by the size of the file and number of targets, respectively.
• Irrespective of the size of the file, BMC Atrium Orchestrator takes a maximum of 200 percent out of 400 percent of CPU for parsing it.

Recommendations

• To limit the size of the BladeLogic export log, only information regarding noncompliant targets should be sent to BMC Atrium Orchestrator. This would help in more scalability and better throughput.
• To tune the performance of the system when the load of noncompliant targets is 10 percent, set the following parameters in BMC Atrium Orchestrator ARS Monitor and ARS Adapter, to enable parallel processing of change requests.