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 provides sizing summaries for environments that incorporate data collection for the Presentation Server.

It is important to estimate the size of your deployment correctly because the steps you follow and the design elements vary depending on the size of the deployment. Use the following sizing and scaling recommendations to prevent oversizing or undersizing your deployment.

The values provided represent the maximum values recommended for the tested parameter.

Note

You can an estimate the environment's size by viewing Infrastructure Management performance diagnostic details in the operator console . The diagnostic details includes information about the server sizing, users, and devices.

 

Sizing chart for data collection by one Presentation Server

Parameter

 Small environment

Large environment

Number of devices

15,000

30,000

Number of events per day1

120,000

800,000

Number of groups

1,500

3,000

Attributes1,600,0004,000,000
Monitored Instances90,000425,000
Number of users25150
Number of concurrent users25100
Number of PATROL Agent Access Control Lists (ACLs)1001000
Number of roles50250
Number of user groups100300
Number of users in each group1010
Number of authorization profiles2550
Number of App Visibility Manager (APM) agents1,0001,000
Number of Central Monitoring Administration (CMA) policies500

Number of concurrent CMA users

1–5

1–5

1. The total number of events per day that a Presentation server can handle includes intelligent events, external events, and App Visibility server events.

Note

For information about the BMC TrueSight Infrastructure Management sizing and scalability considerations, see the Infrastructure Management performance and scalability recommendations .

Related topics

System requirements

Deployment use cases and best practices

 

12 Comments

  1.  

  2.  

    1.  

      1.  

  3.  

    1.  

      1.  

  4.  

  5.  

  6.  

    1.  

  7.