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.

– DATASPACE BP CONTROL BLOCKS = 0 MB (data spaces are not used here)<br />

– DATASPACE LOOKASIDE BUFFER = 0 MB<br />

In our example, buffer pools and control structures use a total of 451.17 MB, which represents<br />

almost 58% of the total DBM1 storage.<br />

Besides the virtual storage required <strong>for</strong> the buffer pools, other components can be large<br />

consumers of virtual storage in the DBM1 address space depending on the workload and<br />

system parameter settings:<br />

► The EDM pool containing active and skeleton plans and packages, dynamic statements,<br />

and Database Descriptors (DBDs). The maximum size is specified by the system<br />

parameter EDMPOOL in DSNZPARM. The storage used is shown by the following<br />

indicator:<br />

– EDM POOL = 146.48 MB<br />

► Compression dictionaries can also consume significant amounts of storage in the DBM1<br />

address space, especially when a compression dictionary is required <strong>for</strong> every partition of<br />

a partitioned table space. The compression dictionary <strong>for</strong> each table space/partition that is<br />

opened. The size of a compression dictionary is 64 KB. The storage required is shown by<br />

the following indicator:<br />

– COMPRESSION DICTIONARY = 0 MB (compression is not used here)<br />

► <strong>DB2</strong> allocates Castout buffers only in a data sharing environment. Castout buffers are<br />

used by <strong>DB2</strong> to read changed pages from the GBP into the DBM1 address space, as a<br />

part of writing them out to disk. Since 128 KB are allocated per castout engine, and you<br />

can have up to 600 castout engines, the total can be up to 77 MB of storage.<br />

– CASTOUT BUFFERS = 0.00 MB (data sharing is not used)<br />

Variable pools<br />

The TOTAL VARIABLE STORAGE contains storage used by threads or agents as working<br />

storage, RID pool, RDS OP pool, Pipe manager subpool (working storage pools used by<br />

parallel tasks), local dynamic statement cache control blocks, thread copies of cached SQL<br />

statements (each thread’s Local Dynamic Statement Cache) and storage <strong>for</strong> various trace<br />

tables. Agent storage is further itemized into storage <strong>for</strong> “system agents” (such as prefetch<br />

engines, deferred write engines, castout engines, GBP write engines, P Lock exit engines)<br />

and “non-system agents”, which includes the number of all active allied threads and active<br />

DBAT threads.<br />

► TOTAL AGENT LOCAL STORAGE = 109.16 MB combines both TOTAL AGENT SYSTEM<br />

STORAGE and TOTAL AGENT NON-SYSTEM STORAGE.<br />

► TOTAL AGENT SYSTEM STORAGE = 3.54 MB. This is the total storage consumed in the<br />

variable pools by the various system agents (<strong>for</strong> example, prefetch engines, deferred write<br />

engines, and castout engines).<br />

► TOTAL AGENT NON-SYSTEM STORAGE = 105.63 MB. This is the total storage<br />

consumed in the variable pools by all the active threads. The normal range <strong>for</strong> <strong>DB2</strong> V8 is<br />

200 KB to 10 MB per thread. Simple threads like CICS transactions can be as low as 200<br />

KB while SAP threads can be as much as 10 MB per thread.<br />

► RID POOL = 0.57 MB. This is the total storage consumed in the variable pools <strong>for</strong> the RID<br />

pool. The RID pool is used <strong>for</strong> list prefetch, multiple index access processing, and hybrid<br />

joins. The maximum size is specified by the DSNZPARM parameter MAXRBLK.<br />

► The Local Dynamic Statement Cache size is indirectly determined by the DSNZPARM<br />

parameter MAXKEEPD when KEEPDYNAMIC(YES) is used. The storage used in the<br />

virtual pools is shown by the following indicators:<br />

160 <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!