Docs.bmc.com will undergo a brief maintenance outage 27 March 2025. The site will be unavailable for ten minutes starting at 6:30 AM CDT/5 PM IST.

Performance tuning for Remedy

This section addresses environments and configurations for typical Remedy enterprise customers, with emphasis on the following tasks:

  • Evaluating the performance of a configuration running Remedy applications
  • Identifying potential bottlenecks that might cause performance issues
  • Collecting and interpreting diagnostic data to identify the root cause of a performance issue

Related topic

Hardware-requirements

Sizing and deployment

Troubleshooting BMC Remedy AR System performance issues

 


The recommendations in this section are based on tests conducted with products running on the BMC Remedy Action Request System server (such as BMC Atrium CMDB, BMC Remedy IT Service Management Suite). However, the majority of the techniques discussed are generic recommendations that can be applied to any product set. To reduce the scope of Remedy performance tuning, these topics focus primarily on the Oracle and Microsoft SQL Server databases and the Tomcat servlet engine.

The following topics contain information on how to tune your Remedy deployment:

Performance considerations

  • Sizing a database server for capacity is important because it might not be possible to scale the database tier horizontally unless you are using Oracle RAC.
  • Database performance is highly dependent on a fast I/O subsystem.
  • Since the AR System server only caches metadata, it is highly dependent on the fast, reliable, low-latency connection to the database.
  • For the AR System server tier, you can scale horizontally by configuring multiple AR System servers configured as a server group.
  • For the web tier, you can scale horizontally by configuring multiple mid tiers connecting to the same AR System server or server group, and by configuring a load balancer (or a reverse proxy) in front of the mid tiers to do the routing.
  • If there is a load balancer or firewall between the mid tier and the AR System server, configure so that idle connections from the mid tier are not severed. Reestablishing severed connections takes additional time.

Best practice

  • We recommend a gigabit connection with close to zero latency between the AR System server and the database. Any additional hop, packet screener, or firewall has a negative impact on performance.
  • We also recommend having a dedicated environment for the Remedy application. Performance is difficult to manage when multiple applications are running in the same environment.


Recommended configurations

See the Knowledge Article KA000114508 for a summary of recommended configurations.