Performance benchmarks and tuning for a PATROL Agent

This topic contains the following information about the performance and network bandwidth utilization of the PATROL Agent. It explains the assumptions used in performance testing, and also lists the PATROL Agent tuning parameters. 

• • Performance testing configuration
  • PATROL Agent tuning parameters
  • PATROL Agent network bandwidth utilization

Performance testing configuration

The data is in this topic is based on the following configuration:

Assumptions used in performance testing

The data is in this topic is based on the following assumption:

• The PATROL Agent and PATROL for VMware vSphere are installed on Microsoft Windows 2012 R2 64-bit.
• The PATROL Agent and PATROL for VMware vSphere are installed on Red Hat Enterprise Linux 7.2 x86_64.
• The PATROL Agent and PATROL for VMware vSphere monitor a large virtual center that comprises 2500 virtual machines.
• The PATROL Agent is connected to BMC Helix Operations Management.
• The network bandwidth between the PATROL Agent and the BMC Helix Operations Management is monitored using tools such as NetLimiter and PerfMon when the PATROL Agent is sending data to BMC Helix Operations Management.
• All the readings are taken in a network bandwidth capacity of 1 Gbps.

PATROL Agent tuning parameters

The following parameters have been documented based on testing the default configuration variables for the data flow between the PATROL Agent and BMC Helix Operations Management:

The data value transfer rate between the PATROL Agent and BMC Helix Operations Management is at 100 parameter values per second.

PATROL Agent network bandwidth utilization

The following table contains information about the network bandwidth utilized between one PATROL Agent and BMC Helix Operations Management.

This data contains the following load:

• vCenter with 2000 devices
• 38000 monitors
• 145000 attributes