Single WebSphere Application Server

Edit online

The tests we ran in the single WebSphere® Application Server setting allowed us to measure throughput differences when using different settings in the Trade application, WebSphere caching, DB2® UDB, networking (caching proxy server, LAN), and using the 64-bit version of WebSphere.

Trade

Caching can be handled in one of three ways in the Trade application. The options are No cache, Command caching, and DistributedMap caching. We ran tests with each of these options. We also varied the number of clients to see how the system reacted when the load is increased.

WebSphere

WebSphere also provides settings that can affect your throughput. You can set your dynamic cache size and vary the number of virtual CPUs for this server. We ran tests adjusting these figures.

Network settings

We also looked at ways to improve throughput via the network settings at the caching proxy server (size of the socket pool, length of time outs) and the z/VM® guest LAN type (QDIO and HiperSockets™).

See Table 1 for our system setup for our single WebSphere Application Server measurements.