Benchmarking results for BMC Remedy Single Sign-on
BMC Remedy Single Sign-on (RSSO) is a new product of the BMC Remedy ITSM suite. RSSO supports SSO integration of the AR Platform with other authentication products such as SAML.
This topic covers the first case of Remedy Single Sign-on (RSSO) 9.1 benchmark, where the RSSO is deployed as in independent service.
BMC built a dedicated setup for RSSO benchmarking. The following table describes servers in this setup:
|Server||Number of Server||Machine||OS|
|Remedy RSSO server 9.1||1||VM with 2 vCPU 8 GB RAM||CentOS 6.5|
|Remedy AR server 9.0||1||VM with 8 vCPU 12 GB RAM||Windows 2008|
|Remedy Mid Tier 9.0||1||VM with 8 vCPU 8 GB RAM||CentOS 6.5|
|Microsoft SQL server 2012||1||Physical machine with 20 cores 512 GB RAM||Windows 2012|
All servers have LAN networking connections.
The following tables describes the BMC Remedy SSO server configuration settings that were used.
Java virtual machine (JVM) settings
Apache Tomcat settings (server.xml)
Keep Alive Timeout
Max Keep Alive Requests
BMC measured Remedy SSO server response time and throughput for the following scenarios:
|Scenario||Workload description||Server Authentication Rate|
|A||540 users with every user login (and logout) once in every 45 seconds||12 requests/second|
|B||540 users with every user login (and logout) once in every 36 seconds||15 requests/second|
RSSO performance load testing results summary
|Workload Description||RSSO Authentication - Response Time (second)||Average % of CPU Utilization|
- Timings reported above are server response times, excluding web browser rendering time. Timings were taken by using Silk Performer timer which measures server response times of the following HTTP requests.
- Give a VM with 2 vCPU, Remedy 9.1 RSSO uses only 7.5 percent of CPU resource and achieves 0.6 second average server response time when the workload is 12 Authentication requests per second.