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.

2.5.9 Unicode parser<br />

Important: Consider setting the page fixing option <strong>for</strong> buffer pools with a poor read hit ratio<br />

and lots of I/O. Balance this setting against the need <strong>for</strong> real storage in the rest of the<br />

system.<br />

For more in<strong>for</strong>mation on page fixing and its per<strong>for</strong>mance implications, refer to Chapter 4,<br />

“<strong>DB2</strong> subsystem per<strong>for</strong>mance” on page 127.<br />

<strong>DB2</strong> must convert all SQL to Unicode since all SQL statements are now parsed in Unicode<br />

UTF-8 <strong>for</strong>mat. This conversion is generally per<strong>for</strong>med by <strong>DB2</strong> invoking z/<strong>OS</strong> Conversion<br />

Services. In addition, the EBCDIC metadata stored in the catalog is converted to Unicode in<br />

CM. After you enable NFM, the metadata is stored in Unicode and the conversion is not<br />

necessary.<br />

If you are using an SBCS code page, the conversion is done directly by <strong>DB2</strong>. If you have a<br />

more complicated code page, then <strong>DB2</strong> invokes z/<strong>OS</strong> Conversion Services.<br />

For more in<strong>for</strong>mation on the Unicode parser and its per<strong>for</strong>mance implications, refer to<br />

Chapter 4, “<strong>DB2</strong> subsystem per<strong>for</strong>mance” on page 127.<br />

2.5.10 Optimizer enhancements<br />

Once you migrate to <strong>DB2</strong> V8 CM, you can choose to rebind your application plans and<br />

packages to possibly get improvements based on the optimizer enhancements to access<br />

paths. For example, fast column processing is re-enabled if you rebind, and your application<br />

can take advantage of the new stage 1 and indexable predicates.<br />

For more in<strong>for</strong>mation on application rebinds, refer to Chapter 4, “<strong>DB2</strong> subsystem<br />

per<strong>for</strong>mance” on page 127.<br />

2.5.11 CF request batching<br />

A new function in z/<strong>OS</strong> V1.4 and CF level 12, called CF request batching, is the ability to allow<br />

multiple pages to be registered to the CF with a single operation. <strong>DB2</strong> V8 takes advantage of<br />

this feature in <strong>DB2</strong> V8 during the actions of registering and writing multiple pages to a GBP<br />

and reading multiple pages from a GBP during castout processing. This new feature really<br />

allows <strong>for</strong> more efficient traffic across the links to and from the CF, and can result in a<br />

reduction of CF processing times and costs associated with data sharing <strong>for</strong> some workloads.<br />

For more in<strong>for</strong>mation on CF request batching, refer to Chapter 8, “Data sharing<br />

enhancements” on page 319.<br />

2.6 New-function mode<br />

The per<strong>for</strong>mance comparisons are generally dependent on the particular workload.<br />

Preliminary measurements in non-data sharing and non-DRDA environments indicate no<br />

significant difference in CPU time overhead in CM versus NFM.<br />

However, in data sharing, the story is much improved. If you are interested in the per<strong>for</strong>mance<br />

impact of a <strong>DB2</strong> V7 application migrated to V8 without any application change and significant<br />

configuration change, there can be a noticeable reduction in V8 overhead going from CM to<br />

22 <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>

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

Saved successfully!

Ooh no, something went wrong!