Trade 6 results
The test results from our DB2 Connect test runs using Trade 6 are detailed here.
The following configuration was used for all Trade 6 measurements.
WebSphere® Application Server 1 z/VM® Guest | WebSphere Application Server 2 z/VM Guest | WebSphere Application Server 3 z/VM Guest | WebSphere Application Server 4 Guest | LPARs | |||||
---|---|---|---|---|---|---|---|---|---|
Memory | CPUs | Memory | CPUs | Memory | CPUs | Memory | CPUs | z/VM CPUs | z/OS® CPUs |
2 GB | 2 | 2 GB | 2 | 2 GB | 2 | 2 GB | 2 | 5 | 6 or 7 |
The WebSphere Application Server configuration parameters for the Trade 6 data source connection pool were configured with 10/100 (min/max) connection entries and the Web Connection Pool Thread size was set to 50/200 (min/max).
In all tests, the Trade 6 brokerage services were configured to use the "direct" method and the number of user IDs was set to 4000.
The number of stock quotes was set to 2000.
The Trade 6 workload driver (WebSphere Studio Workload Simulator) was configured for a think time of 250 milliseconds and distributed all transaction requests in a round robin fashion to each of the WebSphere Application Servers. For example, if 100 users were specified, each WebSphere server was assigned 25 users.