Sizing Windows
You must consider several core technologies when sizing a BMC Cloud Lifecycle Management environment. Sizing of each product in the value path is based on the individual load the sample use case of each product. The following topics are covered in this section:
Sizing by deployment type
The following table explains the sizing requirements for each product in the solution.
Note
Some installations might have specific requirements and complexities that are not reflected here. You must account for these differences when designing a deployment.
Deployment type |
Number of managed devices |
Rate of Change (VM Create, Update, Retire) |
Concurrent Cloud Admins |
Concurrent Cloud End Users |
POC |
1,000 |
10 per hour |
2 |
10 |
Small |
10,000 |
50 per hour |
10 |
50 |
Medium |
25,000 |
100 per hour |
50 |
250 |
Large |
50,000 |
250 per hour |
250 |
500 |
Application tier hardware sizing
The table below describes the number of nodes needed for each deployment size.
Product |
POC |
Small |
Medium |
Large |
Enterprise AR System - Midtier |
None: Services |
2 VCPU 2+GHz |
2 VCPU 2+GHz |
2 VCPU 2+GHz |
Enterprise AR System Server & ITSM Mgmt Suite |
2 VCPU 2+GHz |
2 VCPU 2+GHz x1 |
4 VCPU 2+GHz x2 |
4 VCPU 2+GHz x3 |
Cloud Platform Manager |
2 VCPU 2+GHz |
4 VCPU 2+GHz x1 |
8 VCPU 2+GHz x2 |
8 VCPU 2+GHz x2 |
Atrium Core - Web Registry Components |
2 VCPU 2+GHz |
4 VCPU 2+GHz x1 |
4 VCPU 2+GHz x2 |
4 VCPU 2+GHz x2 |
Cloud Database |
2 VCPU 2+GHz |
4 VCPU 2+GHz x1 |
4 VCPU 2+GHz x2 |
8 VCPU 2+GHz x3 |
BMC Server Automation App Server |
App Server and File Server combined |
8 VCPU 2+GHz x1 |
8 VCPU 2+GHz x2 |
8 VCPU 2+GHz x3 |
BMC Server Automation File Server |
2 VCPU 2+GHz |
4 VCPU 2+GHz x1 |
4 VCPU 2+GHz x2 |
4 VCPU 2+GHz x2 |
BMC Network Automation |
2 VCPU 2+GHz |
2 VCPU 2+GHz x1 |
2 VCPU 2+GHz x2 |
4 VCPU 2+GHz x2 |
BMC Atrium Orchestrator (CDP + CDP HA) |
2 VCPU 2+GHz |
4 VCPU 2+GHz x1 |
4 VCPU 2+GHz x2 |
4 VCPU 2+GHz x3 |
BMC ProactiveNet Performance Management Central Server |
BPPM Central Server combined with Server Leaf and Data Collection |
2 VCPU 2+GHz x1 |
2 VCPU 2+GHz x2 |
2 VCPU 2+GHz x2 |
BMC ProactiveNet Performance Management Server Leaf |
BPPM Central Server combined with Server Leaf and Data Collection |
4 VCPU 2+GHz x1 |
4 VCPU 2+GHz x3 |
4 VCPU 2+GHz x5 |
BMC ProactiveNet Performance Management Data Collection Host |
2 VCPU 2+GHz |
2 VCPU 2+GHz x1 |
2 VCPU 2+GHz x3 |
2 VCPU 2+GHz x5 |
Note
The sizing for BMC Server Automation is based on our test that does not include compliance or auditing. Compliance jobs are CPU intensive. For the use cases that include compliance, use following table.
Product |
POC |
Small |
Medium |
Large |
BMC Server Automation App Server Windows 2008 R2 (64-bit) |
App Server and |
8 VCPU 2+GHz |
8 VCPU 2+GHz |
8 VCPU 2+GHz |
Database tier hardware sizing
You might want to host product databases on single physical server or on separate servers. The decision is based on multiple factors, including, but not limited to hardware and licensing cost, performance, administration & maintenance efforts and security requirements.
This section discusses the sizing factors for hosting product databases on single versus separate servers.
Note
Physical servers are required for the database servers. BMC recommends that you do not run databases on virtualized hardware.
Sizing for separate database servers
The following table provides the sizing guidelines for scenarios where you want to host product databases on separate servers.
Database Instance |
Small |
Medium |
Large |
|---|---|---|---|
Enterprise AR Server Database |
8 CPU-Cores 2+GHz |
16 CPU-Cores 2+GHz |
32 CPU-Cores 2+GHz |
Cloud AR Database |
8 CPU-Cores 2+GHz |
16 CPU-Cores 2+GHz |
32 CPU-Cores 2+GHz |
BMC Server Automation Database |
4 CPU-Cores 2+GHz |
8 CPU-Cores 2+GHz |
8 CPU-Cores 2+GHz |
BMC Network Automation Database |
2 CPU-Cores 2+GHz |
4 CPU-Cores 2+GHz |
4 CPU-Cores 2+GHz |
Note
Above table does not include sizing for POC. We assume that customer will have single database server for POC to minimize hardware requirements.
Sizing for single database server
The following table provides the sizing guidelines for scenarios where you want to host product databases on single servers.
Database Instance |
POC |
Small |
Medium |
Large |
|---|---|---|---|---|
Database Server |
4 VCPU 2+GHz x1 |
16 CPU-Cores 2+GHz x1 |
32 CPU-Cores 2+GHz x2 |
64 CPU-Cores 2+GHz x2+N |
Note
- The disk size mentioned above indicates disk space consumed by the data and indexes. Please include additional space for OS and other software installed.
- The sizing above is based on benchmark tests for CLM specific use cases only
- Transaction Log sizing is mainly driven by two factors, It is recommended that customers should size transaction log files based these factors
- Database recovery model
- DB backup strategy and frequency.
Comments
Log in or register to comment.