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.

4.7.1 Per<strong>for</strong>mance<br />

The improvements in Unicode conversion come from three sources. Each of these sources<br />

affects different facets of conversion per<strong>for</strong>mance, such as the type of characters, and the<br />

length of the character strings. The three sources are:<br />

► <strong>DB2</strong> V8 major and minor conversion: Improves the per<strong>for</strong>mance of all types of<br />

conversions, but the improvements are most dramatic with English alphanumeric<br />

characters because <strong>DB2</strong> does not need to invoke the Unicode conversion service.<br />

► z/<strong>OS</strong> Conversion Services: z/<strong>OS</strong> Release 1.4 implemented an enhancement to z/<strong>OS</strong><br />

Conversion Services with PTF UA05789: This enhancement, referred to as HC3, helps the<br />

per<strong>for</strong>mance of both <strong>DB2</strong> V7 and V8.<br />

► zSeries processor hardware: The z900 model introduced some new Unicode hardware<br />

instructions that are simulated by the z/<strong>OS</strong> Conversion Services on older processors. In<br />

addition, the speed of a z990 engine is approximately 50% faster than the z900 Turbo, but<br />

when it comes to the Unicode conversion of large strings, the z990 hardware is twice as<br />

fast (in this book, we refer to the z900 Turbo model).<br />

Figure 4-19 summarizes the step by step improvements in conversion per<strong>for</strong>mance each of<br />

these sources have made. For these measurements, a single table scan of 1 million rows was<br />

used, using a single cursor with no predicates. The table was defined using 20 VARCHAR<br />

columns per row with 10 characters per column.<br />

Figure 4-19 Conversion per<strong>for</strong>mance overview<br />

Note that the table is not drawn exactly to scale, but it does show the progressive gains in<br />

per<strong>for</strong>mance that have been achieved.<br />

The first bar represents <strong>DB2</strong> V7 running on z/<strong>OS</strong> 1.3 with EBCDIC host variables and<br />

database. CCSID conversion is done here by <strong>DB2</strong> using SYS<strong>IBM</strong>.SYSSTRINGS. Next, we<br />

see a huge jump in CPU time as we ask <strong>DB2</strong> V7 to use Unicode. <strong>DB2</strong> V7 now must invoke<br />

z/<strong>OS</strong> Conversion Services <strong>for</strong> any conversion to and from Unicode. By simply moving to z/<strong>OS</strong><br />

1.4, we see quite a improvement in CPU. This is primarily due to advancements in the z/<strong>OS</strong><br />

Conversion Services that dramatically improved the per<strong>for</strong>mance of (but not exclusively)<br />

conversions between UTF-8 and EBCDIC (or ASCII). The next step in per<strong>for</strong>mance is<br />

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

Conversion per<strong>for</strong>mance overview<br />

<strong>DB2</strong>V7, z900, z/<strong>OS</strong> 1.3, EBCDIC hostvars and database<br />

+UTF-8<br />

database<br />

+ z/<strong>OS</strong> 1.4<br />

+ z990<br />

+ <strong>DB2</strong>V8 (assuming non-alphanumeric)<br />

+ minor conversion (assuming alphanumeric)<br />

+ convert the hostvars to UTF-8 (eliminate conversion)<br />

CPU time

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

Saved successfully!

Ooh no, something went wrong!