Results for the DB2 Connect performance tests

Edit online

After performing our DB2 connect performance tests with the Trade and IRWW workloads, we charted our test results, interpreted the results, and created recommendations.

This chapter provides our detailed test results and conclusions. Tests we performed included:

Considerations for all scenarios

You can relate for all workloads one workload user with an active network connection path from the client via WebSphere®, DB2 Connect, to the DB2 on z/OS. The exception is, when DB2 Connect runs in the connection concentration mode, in that case the number of connections between DB2 Connect and DB2 are fewer than the number of clients connected to DB2 Connect, which means users that doe not get a connection to the database are queued within DB2 Connect.

Parameters common for all test cases

The DB2 Connect configuration parameters were set as follows, unless otherwise specified:
  • NUM_POOLAGENTS = MAX_COORDAGENTS = MAXCAGENTS
  • MAXCONNECTIONS = 1000

The DB2 for z/OS DSNZPARM parameter MAXDBATS was set to 1000.

Note: All guest CPUs described in the following tables are virtual CPUs. The CPUs assigned to the z/VM and z/OS LPARs are physical CPUs.