This page aggregates load test results with the hope that sharing facilitates test practices and supports performance improvements in IdP software.
...
- Throughput remained minimal until a user count of about 25.
- After this initial ramp up of the throughput it remained excellent until the IdP was unable to handle any more traffic.
- The load did have an impact on the average latency, yet this value remained relatively low.
- Average latency remained under 5 seconds until 750 threads test, under 10 seconds until 1500 threads test, and under 15 seconds until 2500 threads test .
- The max latency remained relatively low until about 125 users where it jumped up into non-ideal response times.
- These non-ideal max response times remained consistent until the IdP was unable to handle any more traffic.
- Shown in another test the performance ceiling of the SP was significantly lower than the IdP performance ceiling.
- At 1500 threads the SP for UChicago was unable to respond, and required a restart to resume traffic.
- At 4000 threads the IdP became unresponsive, however after traffic was reduced it was able to recover without a restart.
- The HTTP GET SSO endpoint was the leading failure point of the IdP test case.
...
- CentOS 6 VM with 12G RAM, 1 CPU socket - 4 cores.
- Cisco ACE SLB.
- JVM: Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
- JVM configuration flags:
-server -Xms512 -Xmx4000m - Pooled LDAP for authentication handler and attribute resolver: 12 attributes
- Servlet Container: Jetty 9.2.7
...
- Single IdP node running on CentOS 6 VM (Linux KVM) with 4G RAM and 2 CPUs.
- The IdP host is behind a Brocade ServerIron load balancer.
- JVM configuration flags:
-server -Xmn256m -Xms768m -Xmx2560m -XX:MaxPermSize=256M -XX:+DisableExplicitGC -XX:+UseParallelOldGC - 1 pooled LDAP authentication handler
- 2 pooled LDAP attribute resolvers: 1 for user attributes, 1 for entitlements
- MemoryStorageService
- ComputedPersistentIdGenerationStrategy
...