3.2.3 SMC-D results for IRWW SQLJ OLTP workload  To demonstrate the value of the use of SMC-D in a Db2 environment where the requester and  server are co-located on the same CEC, several measurements were taken by using the  IRWW SQLJ OLTP workload. This workload includes seven different transactions in support  of a warehouse ordering and delivery system. It is the same workload, in terms of the work  that is run, as the standard IRWW workload. The major difference is that it is using static Java  (SQLJ).  On average, each transaction consists of ~15 SQL statements (select/insert/update/delete)  and their associated network messages. The workload is run under USS in one z/OS LPAR,  and connects to a Db2 subsystem on another z/OS LPAR in the same CPC. The  measurements use a Db2 11 for z/OS environment as Db2 12 was still under development at  the time these measurements were taken. Similar results in terms of network latency  improvements are expected with Db2 12 for z/OS. The following performance measurements compare HiperSockets with SMC-D, to  HiperSockets without SMC-D (that is, “old style” HiperSocke ts), and OSA 10 Gb without  SMC-D enabled. The results are shown in Figure 3-7. Figure 3-7 Db2 Class 1 elapsed time From a Db2 class 1 elapsed time perspective, a 19.17% decrease in elapsed time was  observed when SMC-D was used (compared to HiperSockets), and a 70.36% decrease in  elapsed time when compared to the use of OSA 10 Gb. 98  IBM Db2 12 for z/OS Performance Topics