Sizing and scalability considerations
Consider the following sizing and scalability guidelines when planning your deployment.
BMC Application Diagnostics Collector sizing and scaling
Collector database
The following table details the data file storage requirements for the Collector database for small, medium, large and extra large deployments.
Environment size | Total Collector Database size | Request size | Number of breaches per minute | Number of application servers | Number of collector/s | Retention time |
---|---|---|---|---|---|---|
Small | 100 GB | 256 KB | 5 | 20 | 1 | 30 days |
Medium | 260 GB | 256 KB | 25 | 200 | 1 | 30 days |
Large | 550 GB | 256 KB | 50 | 200 | 1 | 30 days |
Extra large | 2100 GB (divided equally among the collectors) | 256 KB | 100 - 200 | 100 - 200 | up to 5 | 30 days |
Database considerations
- The minimum required database size is 100 GB.
- The database size is affected by the request size. For example, in a small environment if the average recorded request size is 1 MB, the required database size will be 400 GB.
Collector software
- The Collector software requires 330 MB.
- Together, the Collector and the Portal require 350 MB.
Maximum assignments
- Maximum BMC Application Diagnostics Agents per Collector = 200
- Maximum BMC Application Diagnostics Collectors per Portal = 5
- Maximum BMC Application Diagnostics Agents per BMC Application Diagnostics Portal = 1000 (divided between up to 5 BMC Application Diagnostics Collectors)
BMC Application Diagnostics Portal sizing and scaling
Portal database
- Requires 1 GB
Portal software
- The Portal software requires 335 MB.
- Together, the Portal and the Collector require 350 MB.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*