Comparison of SQLJ versus JDBC

IRWW provides two methods for driving the workload. One uses SQLJ and the other JDBC. These tests compare the two methods. Two virtual CPUs were defined for the DB2 Connect™ z/VM® guest and 1 GB memory was used. The think time values used for the IRWW workload driver were 2000 milliseconds and 5000 milliseconds and the number of user threads was held constant at 500. The z/VM LPAR was assigned six CPUs and the z/OS® LPAR was assigned four CPUs. The parameter, MAXAGENTS, was set high enough that the number of active connections was not limited.

Figure 1 shows throughput for a DB2 Connect z/VM guest using SQLJ and JDBC with think times of 2000 and 5000 milliseconds.

Figure 2 shows CPU utilization for a DB2 Connect z/VM guest, z/VM LPAR, and z/OS LPAR using SQLJ and JDBC with think times of 2000 and 5000 milliseconds.

Observations

There is little difference between the IRWW JDBC and SQLJ workload drivers.

Conclusion

We selected the SQLJ workload driver because, in our environment, it produces slightly higher throughput at lower CPU utilization.