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.

The following query was utilized:<br />

SELECT X, Y, Z FROM CUSTOMER OPTIMIZE FOR 240001 ROWS FOR FETCH ONLY<br />

All column data is CHAR or VARCHAR<br />

240000 rows at 133 bytes per row were returned resulting in a result set size of 31,920,000<br />

bytes.<br />

Per<strong>for</strong>mance measurement results<br />

See Table 7-1 <strong>for</strong> the results.<br />

Table 7-1 <strong>DB2</strong> connect evaluation <strong>DB2</strong> V7 vs. <strong>DB2</strong> V8<br />

<strong>DB2</strong> Connect and client V8 per<strong>for</strong>med better <strong>for</strong> large result sets with <strong>DB2</strong> V8 as the DRDA<br />

application server compared to <strong>DB2</strong> V7. The retrieval of data from <strong>DB2</strong> V8 is 15.2% faster<br />

than from <strong>DB2</strong> V7. This improvement is achieved through the support of a 64 KB query block<br />

size and the automatic use of multi-row fetch by DDF in <strong>DB2</strong> V8.<br />

Conclusion<br />

The 64 KB query block size can reduce the network transfers by 50% in <strong>DB2</strong> V8 compared to<br />

<strong>DB2</strong> V7.<br />

Recommendation<br />

In order to benefit from the larger query block size supported by <strong>DB2</strong> V8 when dealing with<br />

large result sets, you should update the <strong>DB2</strong> client configuration parameter RQRIOBLK value<br />

to 65,635 since the default is 32,767.<br />

7.1.5 <strong>DB2</strong> Universal Driver <strong>for</strong> SQLJ and JDBC<br />

<strong>DB2</strong> <strong>UDB</strong> <strong>for</strong> Multiplat<strong>for</strong>ms <strong>Version</strong> 8.1 was the first member of the <strong>DB2</strong> Family to introduce<br />

the new JDBC Driver, called the <strong>IBM</strong> <strong>DB2</strong> Universal Driver <strong>for</strong> SQLJ and JDBC. This new<br />

Java driver architecture is the future basis of all <strong>DB2</strong>-related Java ef<strong>for</strong>ts. It supports what is<br />

called the JDBC type 2 and type 4 Driver.<br />

These drivers are currently supported on <strong>DB2</strong> <strong>UDB</strong> <strong>for</strong> Linux, Unix, and Windows and <strong>DB2</strong> <strong>for</strong><br />

z/<strong>OS</strong> <strong>Version</strong> 8. They are also available <strong>for</strong> <strong>DB2</strong> <strong>for</strong> z/<strong>OS</strong> and <strong>OS</strong>/390 <strong>Version</strong> 7, through the<br />

maintenance stream via UQ85607.<br />

Note that with PTF UQ94429 (<strong>DB2</strong> V7) and UQ94430 (<strong>DB2</strong> V8) <strong>for</strong> APAR PQ93458, release<br />

2.3 of the <strong>DB2</strong> Universal Driver became available.<br />

Refer to 7.3, “WebSphere and the <strong>DB2</strong> Universal Driver” on page 292 <strong>for</strong> more in<strong>for</strong>mation.<br />

7.2 Multi-row FETCH and INSERT in DRDA<br />

Elapsed time (sec.) Transfer rate (MB/sec.)<br />

<strong>DB2</strong> V7 7.111 4.28<br />

<strong>DB2</strong> V8 6.176 4.93<br />

Client applications that use the <strong>DB2</strong> CLI/ODBC API could already use multi-row fetch and<br />

insert on the client side. The function SQLExtendedFetch() per<strong>for</strong>ms an array fetch of a set of<br />

rows. Also <strong>for</strong> multiple insert, delete, or update, <strong>DB2</strong> CLI/ODBC provides an array input<br />

Chapter 7. Networking and e-business 285

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

Saved successfully!

Ooh no, something went wrong!