Sizing the Presentation Server
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 each environment type. The number of components connected to the Presentation Server can vary depending on the deployment type and do not affect these values.
Sizing chart for data collection by one Presentation Server
Parameter | |||
|---|---|---|---|
Number of devices | 15,000 | 30,000 | 60,000 |
Number of events per day1 | 120,000 | 600,000 | 1,400,000 |
Number of groups | 1,500 | 3,000 | 9,000 |
Attributes | 1,600,000 | 2,500,000 | 5,000,000 |
Monitored Instances | 90,000 | 350,000 | 750,000 |
Number of users | 25 | 100 | 150 |
Number of concurrent users | 25 | 50 | 100 |
Number of PATROL Agent Access Control Lists (ACLs) | 100 | 250 | 1000 |
Number of roles | 50 | 100 | 250 |
Number of user groups | 100 | 150 | 300 |
Number of authorization profiles | 25 | 100 | 150 |
Number of App Visibility Manager (APM) agents | 1,000 | 1,000 | 1,000 |
Number of Central Monitoring Administration (CMA) policies | 100 | 300 | 500 |
Number of concurrent CMA users | 1–5 | 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.
Related topics
Deployment-use-cases-and-best-practices