Test case scenarios and results

The following section provides a description of the test case scenarios that were used and the observed results for each scenario.

Test case scenarios
Unless otherwise noted, this is the standard test environment for the WebSphere Application Server tests.
Baseline definition parameters and results
These are the parameters used in the baseline testcase, and the results in terms of throughput and CPU utilization.
Vary caching mode
In this test scenario, the Trade application was configured for: No caching, Command caching, and Distributed Map caching. For Command caching, an additional scenario was done with Servlet caching enabled. The objective was to determine which caching mode produced the highest throughput.
Vary garbage collection policy
The impact of the possible JVM garbage collection policies were tested in this scenario.
Vary caching policy
These are a series of test cases that compare the various cache replication sharing policies.
Vary proxy system in the DMZ
This test case compared the results of the tests run with three different environments for the proxy system.
Scaling the size of the DynaCache
This is a series of test cases that compare the various dynamic cache sizes.
Scaling the update part of the Trade workload
In this test case, the update part of the Trade workload was scaled.
Enabling DynaCache disk offload
In these tests, the dynamic cache size was adjusted to a value that would allow the cache to offload entries from real memory to disk.
Comparison between IBM System z9, type 2094–S18 and IBM System z10, type 2097–E26
This test compares the results for client scaling for runs done on the IBM® System z9®, with the results on an IBM System z10®.
Using z/VM VSWITCH
In this test case, the network interface for interconnecting the z/VM® guest systems was changed from a HiperSockets configured guest LAN to a VSWITCH configured LAN.

Parent topic: Tuning WebSphere Application Server Cluster with Caching