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.

Use <strong>DB2</strong> Connect when a high amount of client connections is expected, <strong>for</strong> example, from<br />

applets, in its quality as connection pool/connection concentrator. The measured overhead,<br />

shown in Figure 7-13, is about 2%.<br />

Where possible, use SQLJ. Throughput is higher as well on the server as on the requester<br />

with SQLJ. Static SQL is faster than dynamic SQL, because at run time only the authorization<br />

<strong>for</strong> packages and plans must be checked prior to the execution of the program. In contrast to<br />

that, dynamic SQL statements require the SQL statements to be parsed, table and view<br />

authorization to be checked, and the access path to be determined. Besides better<br />

per<strong>for</strong>mance, SQLJ offers availability and usability benefits over JDBC:<br />

► Less and easier code, easier to maintain<br />

► Authorization on package level<br />

► Easier deployment with the fully portable serialized profile when using the Universal Driver<br />

if compared to the old driver.<br />

Balancing features of JCC with WebSphere V5.1.1 AIX - <strong>DB2</strong> <strong>for</strong> z/<strong>OS</strong> V8<br />

Starting from the GA version of <strong>DB2</strong> Universal Driver FixPak 10, <strong>DB2</strong> has introduced<br />

connection concentrator and sysplex workload balancing features <strong>for</strong> all Java type 4<br />

connections to <strong>DB2</strong> <strong>for</strong> z/<strong>OS</strong> servers. These two new features are built upon the JCC global<br />

object pooling architecture, and are similar in functions to <strong>DB2</strong> Connect's connection<br />

concentrator and sysplex support.<br />

The objective of these measurements is to evaluate the overhead of reusing JCC transports<br />

with connection concentrator and sysplex workload balancing enabled, and compare it to the<br />

overhead of <strong>DB2</strong> Connect and JCC T2 driver.<br />

The IRWW workload was run with the JCC T4 configuration shown in Figure 7-14.<br />

IRWW<br />

Workstation<br />

IRWW<br />

Workload<br />

Driver<br />

Figure 7-14 JCC T4 configuration <strong>for</strong> balancing options<br />

Connection concentrator and sysplex workload balancing are two separate JCC features.<br />

This is different from <strong>DB2</strong> Connect where connection concentrator must be enabled be<strong>for</strong>e<br />

you can exploit sysplex load balancing and failover routing at the transaction boundary. It is<br />

possible to enable connection concentrator or sysplex workload balancing in the JCC data<br />

source custom properties.<br />

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

WebShpere<br />

AIX zSeries<br />

J<br />

C<br />

C<br />

T<br />

4<br />

LPAR D7<br />

DB8A<br />

LPAR D8<br />

DB8B

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

Saved successfully!

Ooh no, something went wrong!