19.06.2013 Views

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

KB<br />

600<br />

500<br />

400<br />

300<br />

200<br />

100<br />

0<br />

Figure 4-5 DBM1 user thread storage comparison <strong>DB2</strong> V7 vs. V8<br />

OTHER includes RDS OP pool (in V7 only), RID pool, and trace tables.<br />

This graph shows that, in general, the DBM1 storage required <strong>for</strong> each thread increases as<br />

we move from <strong>DB2</strong> V7 to V8. Comparing this graph with Figure 4-4, we can conclude the<br />

increase in thread storage is the most significant driver <strong>for</strong> the overall storage increase in the<br />

DBM1 address space, as we move from <strong>DB2</strong> V7 to V8 with distributed applications.<br />

For dynamic SQL, here we can see that more storage is required by <strong>DB2</strong> V8 to prepare the<br />

dynamic SQL. Once again, this increase in storage is needed to support <strong>DB2</strong> functionality<br />

such as processing SQL in Unicode and support <strong>for</strong> long names. We also observe that the<br />

dynamic statement cache (DSC) memory usage has increased.<br />

Tip: PTF UK00991<strong>for</strong> APAR PQ96772 provides significant virtual storage relief <strong>for</strong> large,<br />

dynamic SQL cache environments by moving the DSC control blocks above the bar.<br />

DIST address space<br />

Now, let us turn our attention briefly to the DIST address space, since the total <strong>DB2</strong> demands<br />

on storage extend beyond the DBM1 address space.<br />

Table 4-6 on page 150 compares the virtual storage consumed by active distributed<br />

connections in the DIST address space <strong>for</strong> <strong>DB2</strong> V7 and V8 <strong>for</strong> all distributed workloads we<br />

studied. The table shows quite a significant increase in virtual storage used by active<br />

distributed connections in the DIST address space, from 45% to 169% <strong>for</strong> SQLJ and JDBC<br />

workloads respectively. This increase may not be an issue with distributed inactive thread<br />

processing (CMTSTAT=INACTIVE).<br />

The majority of this growth is stack storage and the variable subpools. These are very<br />

dynamic pools with the storage owned and consumed by thread-related activities.<br />

152 <strong>DB2</strong> <strong>UDB</strong> <strong>for</strong> z/<strong>OS</strong> <strong>Version</strong> 8 Per<strong>for</strong>mance <strong>Topics</strong><br />

DBM1 below 2 GB VS<br />

User Thread Storage Comparison<br />

V7 CLI<br />

V8 CLI<br />

V7 JDBC<br />

V8 JDBC<br />

V7 EMB<br />

V8 EMB<br />

V7 SQLJ<br />

V8 SQLJ<br />

V7 IRWW<br />

V8 IRWW<br />

V7 IRWW DSHR<br />

V8 IRWW DSHR<br />

Other<br />

Stack<br />

DSC<br />

User

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!