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.

oltp<br />

oltp in data sharing<br />

batch insert<br />

batch select<br />

batch fetch/update<br />

batch data sharing<br />

batch drda<br />

utility<br />

query<br />

Figure 4-1 CPU workload summary<br />

CPU range by workload<br />

-20% -10%<br />

0% +10% +20%<br />

The typical customer CPU regression of <strong>DB2</strong> V8 is anticipated to be 0 to 10% more than V7<br />

on average. This CPU degradation is the result of the new functionality that is provided in <strong>DB2</strong><br />

V8, together with the overhead that comes with 64-bit addressing.<br />

Looking at it a little closer, the CPU delta is:<br />

► 0 to +15% regression <strong>for</strong> online transaction workloads<br />

Remember, we have much more code and function in V8 compared with V7, as well as<br />

dealing with the added complication of 64-bit addressing in the DBM1 address space.<br />

► -5 to +10% regression <strong>for</strong> online transaction workloads in data sharing environments<br />

The reason why we are able to achieve less CPU degradation in data sharing is because<br />

there are a number of per<strong>for</strong>mance enhancements in V8 that apply specifically to data<br />

sharing environments. For example, Lock Protocol Level 2 to reduce global lock<br />

contention. See Chapter 8, “Data sharing enhancements” on page 319 <strong>for</strong> more details.<br />

► -5 to +20% regression in batch workloads<br />

– -5 to +5% with a heavy INSERT workload<br />

This does not represent a significant change and is comparable to <strong>DB2</strong> V7.<br />

– -5 to +20% with a heavy SELECT workload<br />

We are able to achieve some CPU reduction <strong>for</strong> SELECT workloads because the<br />

SELECT workloads benefit from the new lock avoidance techniques used in V8. See<br />

4.13.4, “Lock avoidance enhancements” on page 214 <strong>for</strong> more details. Applications<br />

using CURRENTDATA(YES) receive the most benefit as these do not exploit lock<br />

avoidance in <strong>DB2</strong> V7. We see more CPU degradation (up to a 20%) as the number of<br />

columns increases.<br />

– +5% to +20% with a heavy FETCH and UPDATE workload<br />

This increase in CPU varies greatly based on the number of columns being processed.<br />

The more columns, the more CPU used. In fact, you may see as much as 20% more<br />

CPU consumed in V8 when you are processing over 100 columns in the SQL.<br />

► -10% to +15% regression in batch workloads in a data sharing environment<br />

Chapter 4. <strong>DB2</strong> subsystem per<strong>for</strong>mance 131

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

Saved successfully!

Ooh no, something went wrong!