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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

For the same buffer pool size and other configuration settings, in general, a 1 to 20% increase<br />

in demand <strong>for</strong> real storage <strong>for</strong> medium to large <strong>DB2</strong> V8 subsystems is experienced. For<br />

smaller <strong>DB2</strong> subsystems, we experience a higher increase. Measurements have seen as little<br />

as 4 to 5% increase demand <strong>for</strong> real storage, in the workloads used.<br />

Your mileage will definitely vary, depending on the type of <strong>DB2</strong> workload (<strong>for</strong> example, simple<br />

OLTP SQL compared to complex, query-based SQL) and the current demands <strong>DB2</strong> is placing<br />

on your real storage. It is important to ask if <strong>DB2</strong> is a major user of real storage on your<br />

system or a minor user of real storage.<br />

We first compare real storage measurements <strong>for</strong> various distributed workloads. These<br />

scenarios tend to be a “worst case” <strong>for</strong> studying real storage requirements in <strong>DB2</strong> V8,<br />

because the DIST address space storage has also increased in V8, which also drives the<br />

demand <strong>for</strong> real storage in the LPAR. Normally you would see less demand on real storage<br />

when you are only running a local workload since the DIST address space is not used.<br />

Distributed per<strong>for</strong>mance<br />

We can make the following conclusions about the per<strong>for</strong>mance data in Table 4-8.<br />

The real storage used <strong>for</strong> CLI ODBC and embedded SQL workloads is significantly less than<br />

those <strong>for</strong> JDBC and SQLJ. The real storage increase on an LPAR basis is as high as 20% <strong>for</strong><br />

the JDBC workload, compared with 11% <strong>for</strong> the CLI workload.<br />

Table 4-8 Real storage comparison <strong>for</strong> CLI, JDBC, embedded SQL, and SQLJ workloads<br />

Real storage in<br />

MB <strong>for</strong> LPAR<br />

Figure 4-6 illustrates the difference in real storage between <strong>DB2</strong> V7 and V8 <strong>for</strong> the same<br />

series of per<strong>for</strong>mance tests already discussed in this section. We measure the real storage<br />

consumed <strong>for</strong> the different workloads comparing <strong>DB2</strong> V7 usage to that of V8 <strong>for</strong> the DBM1<br />

and DIST address spaces. As you can see, the real storage growth in <strong>DB2</strong> V8 is significant<br />

and something you need to prepare <strong>for</strong>, as you migrate to V8.<br />

154 <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 />

CLI JDBC Embedded SQL SQLJ<br />

V8 V7 to V8%<br />

increase<br />

V8 V7 to V8%<br />

increase<br />

V8 V7 to V8%<br />

increase<br />

V8 V7 to V8%<br />

increase<br />

1196 11% 1410 20% 1175 11% 1238 18%<br />

DBM1 547 24% 688 29% 566 29% 523 25%<br />

DIST 70 64% 137 169% 74 73% 63 45%<br />

IRLM 5 139% 5 139%<br />

MSTR 19 19% 18 19%<br />

OTHER 555 -3% 563 -2% 535 -8% 652 12%<br />

Note: The row name OTHER records the real storage consumed by the whole LPAR minus<br />

those address spaces separately listed in the table.<br />

The real storage values <strong>for</strong> IRLM and MSTR were not separately captured <strong>for</strong> the static<br />

cases; as a result, these times are reflected in the table under OTHER. The real storage<br />

consumed by the IRLM and MSTR address spaces does not have significant changes from<br />

the values already noted <strong>for</strong> the CLI and JDBC tests.

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

Saved successfully!

Ooh no, something went wrong!