The sizing baselines in the following table are based on performance lab benchmark test results and real-world customer experience. For more information about performance tuning and configuration checklist, see the Knowledge Article 000114508.
The basic Remedy deployment model can support up to 800 concurrent users. Concurrent users indicate the number of users logged in and actively working on the system. If your organization is using a significant number of web-based clients (utilizing the mid tier) and the thick-based BMC Remedy client tool, you should calculate the totals for each and use the total number as the estimate for concurrent users.
The following table lists the configuration for the type of deployment:
|Type of deployment||Number of Remedy ITSM concurrent users||Number of Remedy Smart Reporting concurrent users||Number of Digital Workplace users|
The following table lists the sizing baselines for a small deployment:
|Deployed components||Small deployment|
|Only Remedy ITSM stack|
12 CPUs, 36 GB RAM
12 CPUs * 32 GB RAM
8 CPU, 16 GB RAM
|Remedy ITSM stack with Smart IT|
16 CPUs, 48 GB RAM
16 CPUs * 48 GB RAM
8 CPU, 16 GB RAM
|Remedy ITSM stack with Smart IT and Digital Workplace|
24 CPUs, 64 GB RAM
DWP Catalog server with 8 CPU, 16 GB RAM
AR server with 20 CPU, 64 GB RAM
16 CPU, 32 GB RAM
Deployment High Availability (HA) can be accomplished through standard horizontal scaling. The entire deployment model can be duplicated with the original resource allocation in place. The simplest HA can be achieved when the deployment is virtualized; that is, the entire deployment model is duplicated and enough resources are allocated to the VMs.
One example of enabling HA in your environment is that if you are using only the Remedy ITSM stack, then for the Web tier, configure two servers with 12 CPU 36 GB each: one server for primary use and another server for HA. Therefore, by using the sizing guidelines in the preceding table, if you have a single server with 12 CPU, 36 GB RAM for your base web tier, in HA, you would have two servers with 12 CPU, 36 GB RAM.
For information about sizing baselines for medium and large deployments, see the Knowledge Article 000114508.