Sizing baseline

Review the following topics for recommended deployment environment sizing, hardware, database, and Java heap size recommendations: 

Environment sizing 

*Managed devices refers to devices that have an IP address and can be remotely connected over an Ethernet network.

Hardware recommendation

Click here to download a VSDX file (Microsoft Visio 2013) that contains a source copy of this diagram that you can customize to your environment. The following architecture diagram displays specifications for a medium-sized environment.

 Other deployment sizing considerations

• BMC Virtual Chat is deployed on the same Tomcat server on which  the BMC Remedy Mid Tier is installed.
• BMC Remedy Single Sign-On can be deployed on the same Tomcat server on which the BMC Remedy Mid Tier is installed. Ensure that the system has adequate resources to support both the applications.
• A typical MongoDB server requires a three-node deployment: one primary and two secondary. Another option is to deploy MongoDB using two servers: one primary and one secondary, with an arbiter on one of the Smart IT-MyIT servers.
• For Smart IT deployment, add CPU capacity to your AR System servers because Smart IT relies heavily on full-text search (FTS), a CPU intensive process. Refer to Smart IT-My IT benchmark reports for sizing guidelines at Smart IT 1.5 performance .

Hardware considerations for data

• The Atrium Web Registry database is not transactional in nature and therefore much smaller in size. For small, medium, and large deployments, this database can be installed on the same Microsoft SQL Server instance.
• The sizing in the preceding table is based on benchmark tests for specific use cases only.
• Transaction log sizing is mainly driven by the following factors. BMC recommends sizing the transaction log files based on these factors:
  • Database recovery model
  • Database backup strategy and frequency

Database tier sizing recommendation

The following disk sizes indicates the disk space that is occupied by data and indices. Always include additional space for additional data, OS, and any other additional software installed.

Use the following size estimates as guidelines. Conduct benchmarks in your environment to get accurate sizing based on your workload mix, data volumes, and date composition. Download a copy of the planning spreadsheet.

Java heap size recommendation

The following Java heap size requirements are only guidelines. Adjust your Java heap size based on your load conditions. The heap size is set in the arserver.config file (Windows) or arserverd.conf file (Linux or Solaris) located in the ARSystem directory.

Additional JVM garbage collection (GC) parameters

jvm.option.[xx]=-XX:+UseConcMarkSweepGC 
jvm.option.[xx]=-XX:+UseParNewGC 
jvm.option.[xx]=-XX:+UseCompressedOops 
jvm.option.[xx]=-XX:NewRatio=2 
jvm.option.[xx]= -XX:+HeapDumpOnOutOfMemoryError 
jvm.option.[xx]= -XX:HeapDumpPath=<Path> 
jvm.option.[xx]= -XX:ErrorFile=<Path>\hs_error_%p.log 

For information about adding these parameters, see KA000113248 .

How BMC develops deployment recommendations

The BMC Performance Lab conducted a set of online and batch workloads to benchmark the performance and scalability of the BMC IT Service Management Suite and to characterize the system behavior under various workload conditions. The supporting environment and IT infrastructure used for these workloads were constructed to reflect the typical deployment architecture. For more information, see  Benchmark summary.

Related topics

Compatibility matrix

Software dependencies for BMC Remedy AR system

Benchmarking results for BMC Remedy Single Sign-on