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.

JCC Type 4 Direct<br />

4:3 Concentration<br />

JCC Type 4 Direct no<br />

Concentration<br />

<strong>DB2</strong> Connect 4:3<br />

Concentration<br />

<strong>DB2</strong> Connect no<br />

Concentration<br />

Figure 7-16 Per<strong>for</strong>mance of JCC T4 vs. <strong>DB2</strong> Connect<br />

We can observe that the <strong>DB2</strong> Connection concentration degradation is 13.5%, versus the<br />

JCC Type 4 concentration degradation of 12%. The value is very similar.<br />

In determining the choice of function to implement concentration and balancing, keep in mind<br />

that the two options have different characteristics and the requirements of the application<br />

must take into account the considerations summarized in Figure 7-4<br />

Table 7-4 Comparing the key points of the two solutions<br />

<strong>DB2</strong> Connect JCC Driver<br />

Wider scope<br />

<strong>DB2</strong> connect is a gateway. It is aware of all <strong>DB2</strong><br />

requests. it is capable of supporting connection<br />

concentration across multiple JVMs on one or<br />

more machines. JCC driver only runs within the<br />

scope of a single JVM, it is not aware of the<br />

connections of another JVM and it can only<br />

concentrate connections originated from its own<br />

JVM<br />

Connection pooling<br />

Connection pooling allows agents and<br />

connections to be reused by other users and<br />

programs. JCC T4, at the time writing, doesn't<br />

have connection pooling, and it must either rely<br />

on external application server such as<br />

WebSphere or extra programming in standalone<br />

Java applications to support connection pooling.<br />

Ease of software upgrade<br />

From a software management perspective, it is<br />

easier to have the software in one place, any<br />

upgrades only have to be done to the <strong>DB2</strong><br />

Connect Enterprise Edition (EE) server (a<br />

centralized gatekeeper <strong>for</strong> <strong>DB2</strong> servers on z/<strong>OS</strong>),<br />

not to every JCC driver spread throughout the<br />

entire enterprise.<br />

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

JCC T4 vs. <strong>DB2</strong> Connect<br />

369.34<br />

428.84<br />

422.23<br />

0 100 200 300 400 500<br />

487.03<br />

Normalized z/<strong>OS</strong><br />

Transaction /<br />

Second<br />

Better granularity<br />

<strong>DB2</strong> Connect can only specify the maximum<br />

number of coordinator agents allowed at the<br />

server level. it cannot control connection agents<br />

allocated to each JVM. JCC driver allows users to<br />

specify the maximum number of allowed<br />

transport objects at datasource level and at the<br />

driver level. This gives JCC driver much better<br />

granularity to manage transport resources.<br />

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

The per<strong>for</strong>mance measurements show that JCC<br />

T4 has slightly better per<strong>for</strong>mance than <strong>DB2</strong><br />

Connect V8 when running with the same<br />

connection to transport/agent ratio

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

Saved successfully!

Ooh no, something went wrong!