Sizing the Presentation Server for Infrastructure Management data collection
This topic provides sizing summaries for Infrastructure Management 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
Number of devices
Number of events per day1
Number of groups2
|Number of users||50||150||150|
|Number of concurrent users||10||100||100|
|Number of PATROL Agent Access Control Lists (ACLs)||200||1000||1000|
|Number of roles||50||250||250|
|Number of user groups||75||300||300|
|Number of authorization profiles||75||150||150|
|Number of App Visibility Manager (APM) agents||500||1000||1500|
|Number of enabled Infrastructure policies||100||500||1000|
1. The total number of events per day that a Presentation Server can handle includes intelligent events, external events, and App Visibility server events.
2. The test environment had only one group with 50,000 monitor instances and all other groups had an average of 100 monitor instances only. Groups consisted of both auto-sync and manual groups.
Sizing details for KM deployment and PATROL Agent upgrades
For deploying packages and upgrading PATROL Agents, the maximum number of PATROL Agents supported per deployment job is 500.