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 the following operations in an environment that includes data collection and event management:

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

Sample data collection and event management environment

Metric

Amount or value

Number of devices

20 K

Number of groups

2100

Number of monitor instance

100 K (50 K per Integration Service)

Number of intelligent events

5 K per day

Number of attributes

1,000 K

Polling frequency

5 minutes stats, 5 minutes auto-sync

Database size

60 GB

Average database growth per day

1.5 GB

Backup and restore, BMC ProactiveNet Sybase ASA Database

  • BMC ProactiveNet stores up to seven database restore log files: six files from Monday through Saturday, one file with the full backup).
  • Average size of each incremental log file: 1.35 GB
  • Time to restore each incremental log file: 30 minutes
    BMC ProactiveNet stores up to seven database restore log files (six from Monday through Saturday, and one that comes with the full backup).

The following table shows the amount of time necessary to restore a BMC ProactiveNet Sybase ASA Database.

Backup files

Time to restore

1 incremental backup file

30 minutes

1 full backup + 1 incremental backup files

1 hour

1 full backup + 6 incremental backup files

3.5 hours

Startup time for a BMC ProactiveNet Integration Service

The following table shows the startup times for a BMC ProactiveNet Integration Service with a Sybase Database and with an Oracle Database.

Database

Startup time

Sybase Database

7 minutes

Oracle Database

8 minutes


Stop and start times for a BMC ProactiveNet Server

The following table shows the amount of time necessary to stop and start a BMC ProactiveNet Server.

Action

Duration

Stop the server

30 seconds

Start the server

7 minutes

Input/output operations per second for a BMC ProactiveNet Server and Database

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 the embedded Sybase Database on the BMC ProactiveNet Server.

Deployment details

Load details

BMC ProactiveNet Integration Service

Virtual machine

BMC ProactiveNet version

9.0

Operating system

Windows Server 2008 R2

Number of processors

4

Memory

32 GB

Number of devices

20 K (1 K BMC PATROL Agents, 9 K systems)

Number of monitor instances

100 K (50 K per Integration Service)

Number of attributes

1,000 K

Polling frequency

5 minutes stats, 5 minutes auto-sync

In this environment, BMC ProactiveNet Server and Database take approximately 244 IOPS. BMC recommends up to 500 IOPS.

The following diagrams show the IOPS over time for the database and server.

IOPS of BMC ProactiveNet Sybase Database

IOPS of BMC ProactiveNet Server

Network bandwidth utilization between a BMC ProactiveNet Server and Integration Service

In BMC ProactiveNet Server networks, the bandwidth is often measured as the amount of data that is carried from the BMC ProactiveNet Server to the BMC ProactiveNet Integration Service over a specified period.

The following values show the network bandwidth utilization between the BMC ProactiveNet Server and BMC ProactiveNet Integration Service:

  • 50 KB per second
  • Average: 46 KB per second
  • Minimum: 6 KB per second
  • Maximum: 99 KB per second

The following tables give hardware, software, and BMC ProactiveNet Server load details while measuring network bandwidth utilization between the BMC ProactiveNet Server and the BMC ProactiveNet Integration Service.


Upgrade from BMC ProactiveNet version 8.6 Patch 2 to version 9.0

The following tables provide a summary of upgrading from BMC ProactiveNet version 8.6 patch2 to version 9.0. For complete upgrade steps and procedures, refer to BMC ProactiveNet Upgrade Guide. The metrics assume that no configuration changes are required after upgrading, and that all customer updated configuration changes continue as part of BMC ProactiveNet 9.0

Upgrade metrics

Upgrading BMC ProactiveNet with an embedded Sybase Database

The following table gives hardware, software, and BMC ProactiveNet Server load details while measuring the upgrade of BMC ProactiveNet 8.6 with an embedded Sybase Database.

Deployment details

Configuration details

BMC ProactiveNet Agent (Integration service for PATROL)

Virtual machine

BMC ProactiveNet version

9.0

Operating system

Windows Server 2008 R2

Number of processors

4

Memory

32 GB

Load on the system with a Sybase Database

The following table compares different components and metrics on the BMC ProactiveNet Server before and after the upgrade of BMC ProactiveNet 8.6 patch 2 with an embedded Sybase Database.

Metrics

BMC ProactiveNet version 8.6 Patch 2

BMC ProactiveNet 9.0

Database size

20 GB

20 GB

Number of Integration Services

1

1

Number of Self-Monitoring Services

1

1

Events present in the system

14 K closed events, 7 K open events

14 K closed events, 7 K open events

Number of monitor instances

75 K

75 K

Number of instances marked for deletion

3 K

3 K

Number of devices

4 K

4 K

Total number of attributes

525K

525K

Number of groups

650

650

Number of views

10

10

Number of SLOs

50

50

Number of graphs

15

15

Auto-sync poll frequency

15 minutes

15 minutes

Total upgrade time with a Sybase Database

The following table shows the time to update BMC ProactiveNet components for an environment that uses a Sybase Database. The times do not include the restart time of the computer where the BMC ProactiveNet Server is installed.

Upgrade from BPPM 8.6 Patch 2 TO BPPM 9.0

Time

Upgrade of BMC ProactiveNet Server

1 hour, 10 minutes

Upgrade of BMC ProactiveNet Integration Service
(Integration Service upgrade and data collection to resume)

45 minutes

Total time

1 hour, 55 minutes

Upgrading BMC ProactiveNet with an Oracle database

The following table shows hardware, software, and BMC ProactiveNet Server load details while measuring the upgrade of BMC ProactiveNet 8.6 with an Oracle Database.

Deployment details

Configuration details

BMC ProactiveNet Integration Service

Virtual machine

BMC ProactiveNet version

9.0

Operating system

Windows Server 2008 R2

Number of processors

4

Memory

32 GB

Load on the system with an Oracle Database

The following table compares different components and metrics on the BMC ProactiveNet Server before and after upgrade of BMC ProactiveNet 8.6 patch 2 with an Oracle Database.

Metrics

BMC ProactiveNet version 8.6 Patch 2

BMC ProactiveNet 9.0

Database Size

83 GB

83 GB

Number of Integration Services

1

1

Number of Self-Monitoring Service

1

1

Events present in the system

5734

9253

Number of monitor instances

50K

50K

Number of instance marked for deletion

2542

2290

Number for devices

4314

4314

Total number of attribute

525 K

525 K

Number of groups

500

500

Number of views

30

30

Number of SLOs

50

50

Number of graphs

230

230

Auto-sync polling frequency

15 minutes

15 minutes

Total upgrade time with an Oracle Database

The following table shows the time to update BMC ProactiveNet components for an environment that uses an Oracle Database. The times do not include the restart time of the computer where the BMC ProactiveNet Server is installed.

Upgrade from 8.6 Patch 2 to 9.0

Time

Upgrade of BMC ProactiveNet Server

1 hour, 15 minutes

Upgrade of BMC ProactiveNet Integration Service
(Integration Service upgrade and data collection to resume)

1 hour, 10 minutes

Total time to upgrade from 8.6 Patch 2 to 9.0

2 hours, 25 minutes