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

The following tables provide sizing summaries for an environment that incorporates data collection, event management, and impact management:

Provided values represent the maximum values recommended for the tested parameter.

Sizing chart for BMC ProactiveNet Consoles

Characteristic

Small environment

Medium environment

Large environment

Concurrent number of users — BMC ProactiveNet Operations Console

25

50

100

Concurrent number of users — BMC ProactiveNet Administration Console

1

1

1

Data and service model metrics

Characteristic

Small environment

Medium environment

Large environment

Number of devices

5 K

10 K

20 K

Total number of attributes

250 K

500 K

1200 K

Total number of monitor instances on the BMC ProactiveNet Server

15 K

50 K

120-150 K

Maximum number of monitor instances per monitor type

5 K

30 K

70 K

Maximum number of monitor instances per Integration Service 1

8 K

25 K

50 K

KPI Mode

Yes

Yes

Yes

Duration RAW data retention

1 month

1 month

1 month

Duration RATE data retention

3 months

3 months

3 months

Number of Integration Services

1

3

5

Adapter type

PATROL

PATROL

PATROL

Polling frequency, in minutes
(stats, auto-sync)

5, 5

5, 5

5, 5

Number of CIs

5 K

10 K

20 K

Maximum number of CIs per service model

5 K

10 K

20 K

Number of service models

15

25

50

Service model depth

5 levels

6 levels

6 levels


1 You can divide the load between Integration Services according to your deployment type.

Note

  • Do not exceed 50 K instances or 500 K attributes per Integration Service while using a 64-bit BMC ProactiveNet Integration Service. Even providing additional CPU and memory does not help in scaling beyond 50K instance or 500 K attributes per Integration Service.
  • The BMC ProactiveNet Integration service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

Sizing chart for event management

Characteristic

Small environment

Medium environment

Large environment

Number of intelligent events per day 1

10 K

20 K

40 K

Number of external events per day 1

50 K

100 K

200 K

Burst of external events every 1 hour for 3 hours

10 K

20 K

30 K

Number of remote cells

0

5

10

Duration of event retention

Default

default

default

Closure policy used for external events 2

4 hours

4 hours

4 hours

1 Rate is based on events that are evenly distributed in a day.
2 All open external events are closed every fourth hour.

Sizing chart for memory configuration (MaxHeap metrics)

Characteristic

Small environment

Medium environment

Large environment

Size of Jserver MaxHeap

2 GB

4 GB

8 GB

Size of rate MaxHeap

2 GB

4 GB

8 GB

Size of agent controller MaxHeap

1 GB

2GB

4 GB

Size of Self-Monitoring Service MaxHeap

default

default

default

Size of Integration Service

2 GB

4 GB

8 GB