This documentation supports the 9.1 version of Remedy Single Sign-On.

To view the latest version, select the version from the Product version menu.

Benchmarking results for Remedy SSO 9.1.03

This topic covers the first case of Remedy Single Sign-On (Remedy SSO) 9.1.03 benchmark, where Remedy SSO is deployed as an independent service.

Approach

JMeter was used as a tool to create high load instead of SilkPerformer.

The ramp up period for 540 concurrent users with these parameters is approximately 4.5 minutes. Overall run time for each test is approximately 38 minutes. Remedy SSO Server is configured to use AR authentification.

Test Environment

Server type
OS
CPU & Memory
JVM
Comments
Remedy SSO Server and Remedy SSO Sample AppCent OS

8 CPU

16 GB

-Xms4096m - Xmx4096mVirtual machine
JMeterWindows

8 CPU

16 GB

-Xms4096m - Xmx4096mVirtual machine
ARWindows

2 CPU

16 GB

 Virtual machine
DB (SQL Server)Windows

40 CPU

512 GB

 Physical machine

Testing Authentication Performance

The following performance test was done to compare throughput (login requests per second) between two different scenarios.

ScenariosSamplesAverage response time of the login processMin (ms)Max (ms)Std. DevCPU (%) on Remedy SSO ServerThroughputError (%)
Scenario 150161108103423181.441.527.90
Scenario 24977460303198.691.527.80

Testing Session Validation Performance

All the following test runs were done with the same JMeter's test plan (with a different value for the token-status-cache-timeout parameter on Remedy SSO Agent's side). Each user in the test plan has a session live with 10 minutes duration and during this session, a user requests a resource each 10 seconds. Remedy SSO Server is configured to use AR authentication.

User session timeout on Remedy SSO Agent (seconds)Total count of concurrent usersAverage response time of the login process (POST to/rsso/login) in msAverage response time of the logout process (GET to / sample /loggedout.jsp) in msTotal count of GET requests to the test resourceAverage response time to the test resource (ms)Min (ms)Max (ms)Std. Dev. (ms)Throughput (request/s)Total number of requests to verify the token on Remedy SSO Server side (from rsso.log/Tomcat/access log)CPU (%) on Remedy SSO ServerErrors (%)
3054080997200411052.7738.8324000.90
18054082997200311042.5638.964800.70
86400540108109720031952.4538.916200.90



Was this page helpful? Yes No Submitting... Thank you

Comments