Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

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

Compact Deployment (if you use an external database)

5,000

50 per hour

5

25

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

Note

The following table does not include sizing for Compact Deployment. You use a single VM for Compact Deployment to minimize hardware requirements.

The table below describes the number of nodes needed for each deployment size.

Product

Small 
50 Peak Concurrent Users 
10,000 VMs

Medium 
250 Peak Concurrent Users 
25,000 VMs

Large 
500 Peak Concurrent Users 
50,000 VMs

BMC AR System Server – Cloud Portal and Database (Cloud Portal and Database)
Windows 2012 R2 (64-bit) 
Oracle JDK/JRE 1.7 
Apache 2.2 (32-bit) 
Tomcat 6.0.26 (64-bit) 
BMC Remedy AR System Server 8.1 SP1  
BMC Remedy SRM 8.1 SP1 
BMC Cloud Lifecycle Management 4.1

2 VCPU 2+GHz x1 
8 GB RAM 
60 GB Disk

4 VCPU 2+GHz x2 
8 GB RAM 
60 GB Disk

4 VCPU 2+GHz x3 
8 GB RAM 
60 GB Disk

Cloud Portal and Database Mid Tier 
Windows 2012 R2 (64-bit) 
Oracle JDK/JRE 1.7 
Apache 2.2 (32-bit) 
Tomcat 6.0.26 (64-bit) 
BMC Remedy AR System Mid-Tier 8.1 SP1 
2 VCPU 2+GHz 
x1   
4 GB RAM 
60 GB Disk
2 VCPU 2+GHz 
x2  
4 GB RAM 
60 GB Disk
2 VCPU 2+GHz 
x3  
4 GB RAM 
60 GB Disk

Cloud Platform Manager 
Windows 2012 R2 (64-bit) 
Oracle JDK/JRE 1.7 
BMC Cloud Lifecycle Management 4.1

4 VCPU 2+GHz x1  
8 GB RAM
60 GB Disk

8 VCPU 2+GHz x2
8 GB RAM
60 GB Disk

8 VCPU 2+GHz x2
8 GB RAM
60 GB Disk

Atrium Core - Web Registry Components 
Windows 2012 R2 (64-bit) 
Oracle JDK/JRE 1.7 
BMC Atrium Core 8.1 SP1 

4 VCPU 2+GHz x1 
8 GB RAM
60 GB Disk

4 VCPU 2+GHz x2
8 GB RAM
60 GB Disk

4 VCPU 2+GHz x2
8 GB RAM
60 GB Disk

BMC Server Automation App Server    
Windows 2012 R2 (64-bit) 
BMC Server Automation 8.5

8 VCPU 2+GHz x1 
16 GB RAM
60 GB Disk

8 VCPU 2+GHz x2 
16 GB RAM
60 GB Disk

8 VCPU 2+GHz x3 
16 GB RAM
60 GB Disk

BMC Server Automation File Server 
Windows 2012 R2 (64-bit) 
BMC Server Automation 8.5

4 VCPU 2+GHz x1 
8 GB RAM 
200 GB Disk

4 VCPU 2+GHz x2 
8 GB RAM 
200 GB Disk

4 VCPU 2+GHz x2 
8 GB RAM 
200 GB Disk

BMC Network Automation 
Windows 2012 R2 (64-bit) 
BMC Network Automation 8.5

2 VCPU 2+GHz x1
8 GB RAM 
60 GB Disk

2 VCPU 2+GHz x2  
16 GB RAM 
60 GB Disk

4 VCPU 2+GHz x2  
32 GB RAM 
60 GB Disk

BMC Atrium Orchestrator (CDP  + CDP HA) 
Windows 2012 R2 (64-bit) 
BMC Atrium Orchestrator Platform 7.6.02
BMC Atrium Orchestrator Content 4.1

4 VCPU 2+GHz x1 
8 GB RAM 
60 GB Disk

4 VCPU 2+GHz x2 
8 GB RAM 
60 GB Disk

4 VCPU 2+GHz x3 
8 GB RAM 
60 GB Disk


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

Small 
50 Peak Concurrent Users 
10,000 VMs

Medium 
250 Peak Concurrent Users 
25,000 VMs

Large 
500 Peak Concurrent Users 
50,000 VMs

BMC Server Automation App Server 

Windows 2012 R2 (64-bit) 
BMC Server Automation 8.5

8 VCPU 2+GHz  
x1  
20 GB RAM 
60 GB Disk

8 VCPU 2+GHz
x3  
20 GB RAM
60 GB Disk

8 VCPU 2+GHz 
x5 
20 GB RAM
60 GB Disk

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

Note

The following table does not include sizing for Compact. You use a single database server for Compact Deployment to minimize hardware requirements.

The following table provides the sizing guidelines for scenarios where you want to host product databases on separate servers.

Database Instance

Small

Medium

Large

Cloud Portal and Database Server + 
Atrium Web Registry Database 
Windows 2012 R2 (64-bit) 
MS-SQL 2008 Enterprise Edition SP 1 (64-bit)

8 CPU-Cores 2+GHz 
x1 
16 GB RAM 
Data File: 16 GB 
Log File: 3 GB

16 CPU-Cores 2+GHz 
x2 
16 GB RAM  Data File: 26 GB Log File: 3 GB

32 CPU-Cores 2+GHz 
x2 
32 GB RAM 
Data File: 41 GB 
Log File: 3 GB

BMC Server Automation Database 
Windows 2012 R2 (64-bit) 
MS-SQL 2008 Enterprise Edition SP 1 (64-bit)

4 CPU-Cores 2+GHz 
x1 
8 GB RAM  
Data File: 15 GB Log File: 2 GB

8 CPU-Cores 2+GHz 
x2 
8 GB RAM  
Data File: 25 GB Log File: 2 GB

8 CPU-Cores 2+GHz 
x2 
16 GB RAM  
Data File: 50 GB Log File: 2 GB

BMC Network Automation Database 
Windows 2012 R2 (64-bit) 
MS-SQL 2008 Enterprise Edition SP 1 (64-bit)

2 CPU-Cores 2+GHz 
x1 
4 GB RAM   
Data File: 20 GB Log File: 2 GB

4 CPU-Cores 2+GHz 
x2 
8 GB RAM   
Data File: 30 GB Log File: 2 GB

4 CPU-Cores 2+GHz 
x2 
8 GB RAM   
Data File: 80 GB Log File: 2 GB

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

Compact

Small

Medium

Large

Database Server 
Windows 2012 R2 (64-bit) 
MS-SQL 2008 Enterprise Edition SP 1 (64-bit) 
3 separate database instances: 
Cloud Portal and Database Server + Atrium Web Registry 
BMC Server Automation Database
BMC Network Automation Database

8 VCPU 2+GHz x1 
16 GB RAM 
60 GB Disk

16 CPU-Cores 2+GHz x1  
32 GB RAM  
80 GB Disk

32 CPU-Cores 2+GHz x2
32 GB RAM  
120 GB Disk

64 CPU-Cores 2+GHz x2+N  
64 GB RAM 
210 GB Disk

Note

  • The disk size mentioned above indicates disk space consumed by the data and indexes. Include additional space for OS and other software installed.
  • Atrium Web Registry database is not very transactional in nature and hence much smaller in size.  For all Small, Medium and Large deployments, you can install this database on the same SQL server instance.
  • The sizing above is based on benchmark tests for CLM specific use cases only
  • Transaction Log sizing is mainly driven by two factors. Customers should size transaction log files based on the following factors:
    • Database recovery model
    • DB backup strategy and frequency.

Related topics

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments