Sizing baseline
Review the following topics for recommended deployment environment sizing, hardware, database, and Java heap size recommendations:
Environment sizing
Environment | BMC Remedy ITSM (concurrent users) | BMC Remedy Smart Reporting (concurrent users) | Maximum number of managed devices* |
---|---|---|---|
Proof of concept (POC) | 50 | 5 | 1,000 |
Small | 800 | 50 | 2,000 |
Medium | 2,000 | 100 | 10,000 |
Large | 5,000 | 250 | 30,000 |
*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.
Note
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.
Component | POC | Small | Medium | Large |
---|---|---|---|---|
BMC Remedy AR System mid tier servers | None: Services combined with AR System server | Two servers: | Two servers: | Five servers: |
BMC Remedy AR System Web Services | None: Services combined with AR System server | One server: | One server: | Two servers: |
BMC Remedy Single Sign-on | None: Services combined with AR System server | One Server: | Two Servers: | Four Servers: |
BMC Remedy Smart Reporting | One server: 2 CPU core 12 GB RAM 60 GB disk space | One server: 4 CPU core 12 GB RAM 200 GB disk space | Two server: | Two servers: |
BMC Remedy AR System server (user-facing) User-loaded servers | One server: | Two servers: | Three servers: | Four servers: |
BMC Remedy AR System server (back end) Non-user-loaded servers for back-end BMC Remedy AR System processes, integrations, reconciliations, and notifications | One server: | Two servers: | Two servers: | Two servers: |
BMC Remedy with Smart IT | None: Services combined with AR System server | One server: | Two servers: | Three servers: |
BMC Digital Workplace | For more information, see
BMC Digital Workplace Sizing and scalability considerations
|
The sizing specification is for each server or node in a cluster.
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.
Component | POC | Small | Medium | Large |
---|---|---|---|---|
Master BMC Remedy AR System Database | 1 server: | One cluster: | One cluster: | One cluster: |
Replicated BMC Remedy AR System Database for Reporting | None: Services combined with AR System database | One server: | One server: | One server: |
Mongo DB (social database for Smart IT and MyIT) | -- | 3-node MongoDB replica set cluster: 2 CPU core | 3-node MongoDB replica set cluster: 4 CPU core | 3-node MongoDB replica set cluster: 4 CPU core |
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.
jvm.maximum.heap.size | Concurrent users | Memory size | |
---|---|---|---|
Medium | 8589934592 | 800–2,000 | 16 GB |
Large | 21474836480 | 2,000–5,000 | 32 GB |
Set jvm.minimum.heap.size to the same value as jvm.maximum.heap.size.
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.
Comments