Deployment sizing requirements
TrueSight Automation Console supports a variety of deployment configurations. Most configurations require the TrueSight Automation Console database and application to be installed on separate servers.
Minimum deployment sizing requirements
The following table describes minimum requirements based on various deployment sizes.
Requirement | Large | Medium | Small | Minimum space required for installation (GB) |
|---|---|---|---|---|
Number of | 150 | 50 | 25 | |
Automation Console server requirements | ||||
Number of | 6 | 2 | 1 | |
CPUs per | 8 | 8 | 8 | |
Automation Console | 32 | 32 | 32 | 10 |
Automation Console | 100 | 100 | 100 | 10 |
Database server requirements | ||||
CPUs per | 32 | 16 | 8 | |
Database | 64 | 32 | 16 | 8 |
Database | 150 | 120 | 100 | 25 |
A small deployment assumes that the database and the application are hosted on the same server. Memory requirements refer to total memory, not heap size.
If you require a deployment larger than the Large deployment described above, extrapolate the system requirements based on the information in the table.
What conditions were used to develop these sizing requirements?
Condition | Value |
|---|---|
Number of existing vulnerabilities instances in the database | 9 million |
Average time for loading the dashboard at 9 million | 1 minute |
Number of servers managed by the Automation Console | 30000 |
Number of concurrent users (per node) | 15 |
Maximum scan data file size | 1GB |
Number of servers scanned for the missing patches | 1500 |
Average number of missing patches per server | 60 |