2.4 Horizontal and Vertical Scale

These tests include the following Access Manager operations:

NOTE:For more information, see Test Environment: Vertical and Horizontal Scalability.

2.4.1 Login Performance

This scope of this test is measuring the login performance when a user accesses the resource protected with the Secure Name Password Form contract.

Login Performance with CPU Scaling

In this test, memory is kept constant at 32 GB and Tomcat is assigned with 16 GB in Identity Server and Access Gateway. CPUs are increased in the following order 1, 2, 4, 8, and 16 and performance is measured at each CPU level.

Login Performance with Memory Scaling

In this test, the number of CPU is kept constant at 16 for Identity Server and Access Gateway. Memory is increased in the order 8 GB, 16 GB, 32 GB, and 64 GB. Also, Tomcat is assigned with 70% of the available memory. Performance is measured at each memory level.

Login Performance with Number of Nodes in the Cluster

In this test, each node is assigned 8 CPU and 16 GB memory. Performance is measured by increasing the number of nodes in the cluster.

2.4.2 Scalability of Active Users Sessions

Test: Scaling and maintaining the active users sessions by periodically increasing users' logins and refreshing the active session within session timeout period.

Active Sessions Scalability with Scaling CPU

In this test, memory is kept constant at 32 GB and Tomcat is assigned 16 GB in Identity Server and Access Gateway. The number of CPU is increased in the order 1, 2, 4, 8, and 16, and performance is measured at each CPU level.

Active Sessions Scalability with Scaling the Memory

In this test, the number of CPU is kept constant at 16 for Identity Server and Access Gateway. Memory is increased in the order 8 GB, 16 GB, 32 GB, and 64 GB. Tomcat is assigned with 70% of the available memory. Performance is measured at each memory level.

2.4.3 Access Gateway Hits Scalability

Test: Accessing a public resource through Access Gateway. Public resources are static pages of size 60 KB containing several hyperlinks to the same originating web server. In this test, the number of hits per second is measured.

Access Gateway Hits with Scaling CPU

The memory is kept constant to 32 GB and Tomcat is assigned 16 GB for Access Gateway. The number of CPU is increased in the order 1, 2, 4, 8, and 16. Performance is measured at each CPU.

Access Gateway Hits with Scaling the Memory

In this test, CPUs are kept constant at 16 for Access Gateway. Memory is increased in the order 8 GB, 16 GB, 32 GB, and 64 GB. Tomcat is assigned with 70% of the available memory. Performance is measured at each memory level.

2.4.4 Access Gateway Throughput Scalability

Test: Accessing a public resource through Access Gateway. The public resources are static pages of size 8 MB that have several hyperlinks pointing to the same originating web server. Measure the throughput per second.

Access Gateway Throughput with Scaling CPU

In this test, memory is kept constant at 32 GB and Tomcat is assigned 16 GB for Access Gateway. The number of CPU is increased in the order 1, 2, 4, 8, and 16. The performance is measured at each CPU level.

Access Gateway Throughput by scaling the Memory

In this test, the number of CPU is kept constant at 16 for Access Gateway. Memory is increased in the order – 8 GB, 16 GB, 32 GB, and 64 GB. Tomcat is assigned with 70% of the available memory. Performance is measured at each memory level.