Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This topic presents timing approximations for BMC Cloud Lifecycle Management operations when integrated with a BMC ProactiveNet environment that includes data collection, event management, and impact management.

The following environment is used as a sample for the timing estimates.

Sample data collection, event management, and impact management environment

Metric

Amount of value

Number of devices

10K

Number of groups

11

Number of monitor instance

52 K

Attribute

100 K

Polling frequency

5 minutes stats, 5 minutes auto-sync

Database size

 

The following table shows the VirtualCenter details used for monitoring in the testing environment.

Metric

VirtualCenter 1

VirtualCenter 2

VMware VirtualCenter version

4.0.0, 208111

4.1.0, 2587902

Number of data centers

4

6

Number of ESX servers

156

41

Clusters per VirtualCenter

7

5

Number of resource pools in the VirtualCenter

107

275

Number of virtual machines

2300

2900

Stop and start times for BMC ProactiveNet processes

The following table shows the amount of time necessary to stop and start BMC ProactiveNet processes in a BMC Cloud Lifecycle Management environment.

Action

Duration

Stop BMC ProactiveNet processes

30 seconds

Start BMC ProactiveNet processes

7 minutes

Input/output operations per second for a BMC ProactiveNet Child Server

The input/output operations per second (IOPS) in a BMC ProactiveNet 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 gives hardware, software, and BMC ProactiveNet Server load details, and the resulting IOPS for for the embedded Sybase Database on the BMC ProactiveNet Server.

Deploment details

Load details

BMC ProactiveNet Child Server

Virtual machine

BMC ProactiveNet version

9.0

Operating system

Windows Server 2008 R2

Number of processors

4

Memory

12 GB

Number of devices

10K VMs

Number of monitor instances

52 K

Number of attributes

100 K

Polling frequency

5 minutes stats, 5 minutes auto-sync

IOPS of BMC ProactiveNet Sybase Database

IOPS of BMC ProactiveNet Child Server

BMC ProactiveNet Child Server Database, Size growth

Network bandwidth utilization between the BMC ProactiveNet Central Server and Data Collection Host

The network bandwidth utilization is often measured as the amount of data that is transferred from the BMC ProactiveNet Central Server to the BMC ProactiveNet Child Server, and from the BMC ProactiveNet Child Server to the Data Collection Host (comprising of BMC ProactiveNet Integration Service and PATROL Agents) over a specified period.

The following tables shows the hardware and software that is used while measuring network bandwidth utilization between the BMC ProactiveNet Central Server and BMC ProactiveNet Child Server, and between the BMC ProactiveNet Child Server and the Data Collection Host

The following values show the network bandwidth utilization for traffic between the BMC ProactiveNet Central Server and BMC ProactiveNet Child Server:

  • Average: 12.272 KB per second
  • Minimum: 8 KB per second
  • Maximum: 29 KB per second

The following values show the network bandwidth utilization for traffic between the BMC ProactiveNet Child Server and the Data Collection Host:

  • Average: 16.489KB KB per second
  • Minimum: 12 KB per second
  • Maximum: 26 KB per second

Time to provision 50 VMs

The testing environment shows the time to provision 50 VMs through the BMC Cloud Lifecycle Management Planner as 1 hour, 30 minutes.

The time is calculated from raising a request to provision 50 VMs through BMC Cloud Lifecycle Management Portal, to the creation of VMs with corresponding PODs and network containers and the required aggregate monitors, and start collecting data at the BMC ProactiveNet Server.