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.

8.5 Miscellaneous items<br />

In this section we describe some miscellaneous enhancements that impact <strong>DB2</strong> data sharing.<br />

8.5.1 Impact on coupling facility<br />

You do not need to resize the group buffer pools, lock structure or SCA in the coupling facility<br />

as a result of moving to <strong>DB2</strong> V8, even though the virtual buffer pools have now moved above<br />

the bar and have a longer memory address. This is true provided of course, you have not<br />

made any significant changes when you migrate to <strong>DB2</strong> V8.<br />

However, you may wish to review your coupling facility structure sizes after you have migrated<br />

to <strong>DB2</strong> V8. For example, you may like to revise your virtual buffer pool sizes now that there<br />

are no hiperpools or buffer pools in data spaces.<br />

We do recommend you review your coupling facility structure sizes as you prepare to<br />

implement CFLEVEL 12. This is required to take advantage of the CF Request Batch<br />

per<strong>for</strong>mance enhancements, described earlier. When migrating CFLEVELs, coupling facility<br />

structure sizes might need to be increased to support the new function. For example, when<br />

you upgrade from CFLEVEL 9 to CFLEVEL 11 or from CFLEVEL 10 to CFLEVEL 12, the<br />

required size of the structures might increase by up to 768 KB.<br />

The following “Rule of Thumb” <strong>for</strong>mulas may be used to estimate the required coupling facility<br />

structure sizes, based on migrating from CFLEVEL 10 or 11 to CFLEVEL 12. The thumb rules<br />

are only rough approximations.<br />

CFLEVEL 12 structure size = CF level 10 (or 11) structure size PLUS the following based<br />

on type of structure and entry:element ratio:<br />

Lock structure:<br />

Without record data: 0<br />

With record data: 20% of level 10 or 11<br />

List or cache structure:<br />

No data (no elements): 0<br />

Entry:element ratio = 1:1: 2MB + 10%<br />

Entry:element ratio >= 100:1(scale % factor <strong>for</strong> ratios in between): 2MB + 50%<br />

and should only be used if methods 2 and 3 are not applicable.<br />

For example, given a <strong>DB2</strong> group buffer pool structure of 100 Mb, and an entry:element ratio of<br />

5:1 and you are at CFLEVEL 10, then CFLEVEL 12 will require an extra:<br />

100 + 2 + 12% x 100 = 114 MB<br />

If the higher CFLEVEL is accessible in your configuration and is defined in the CFRM policy,<br />

and OW54685 is applied, then structure rebuilds from lower CFLEVELs to higher CFLEVELs<br />

will resize the structure automatically based on its current structure object counts.<br />

Alternatively, we suggest you use the CFSIZER to check your coupling facility structure sizes.<br />

The CFSIZER can be found at:<br />

http://www.ibm.com/servers/eserver/zseries/cfsizer/<br />

8.5.2 Improved LPL recovery<br />

Prior to <strong>DB2</strong> V8, when you issue the -START DATABASE command to recover LPL pages, the<br />

command must drain the entire table space or partition. The "drain" means that the command<br />

must wait until all current users of the table space or partition reach their next commit point.<br />

336 <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>

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

Saved successfully!

Ooh no, something went wrong!