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.

= MVS EXTENDED REGION SIZE (MAX) - MVS 31 BIT EXTENDED LOW PRIVATE<br />

or<br />

1628.00 - 24.64 = 1603.36 MB<br />

► C is the basic cushion constant of 200 MB.<br />

► F is the value <strong>for</strong> fixed areas<br />

or<br />

= TOTAL GETMAINED STORAGE + TOTAL GETMAINED STACK STORAGE + TOTAL FIXED STORAGE<br />

599.18 + 26.77 + 0.30 = 626.25 MB<br />

The maximum theoretical number of threads can there<strong>for</strong>e be estimated as:<br />

V/TF<br />

For our example, the theoretical maximum number of threads can be estimated as:<br />

(1603.36 - 200 - 626,25) / 0.3 = 777.11 / 0.30 = 2590.37.<br />

This is also reported in the report as MAX NUMBER OF P<strong>OS</strong>SIBLE THREADS as 2593.01.<br />

The difference between 2590 and 2593 can be explained because the above calculation is<br />

based on the rounded MB values of the report, while Per<strong>for</strong>mance Expert uses the exact byte<br />

values of IFCID 225.<br />

Be warned that this is a maximum theoretical limit and should only be used as a guide or<br />

rough estimate. It does not provide <strong>for</strong> things such as growth in buffer pools and more<br />

compression dictionaries that may be required to support the extra workload.<br />

The stack storage size is directly proportional to the number of threads, not FIXED. Even<br />

Getmained ones are really not fixed. Threads would typically be much bigger in an<br />

environment which has many more threads. If a measurement run has 100 threads and the<br />

maximum is calculated much higher <strong>for</strong> the projection, such as 1000, the result in the<br />

maximum number of threads allowed tends to be much higher than really possible.<br />

So, what has changed in <strong>DB2</strong> V8?<br />

Example 4-2 shows the same extract from a <strong>DB2</strong> PE V8.1 Statistics Long Trace, but this time<br />

it shows the DBM1 STORAGE STATISTICS section <strong>for</strong> a <strong>DB2</strong> V8 subsystem. Once again, the<br />

report was produced with the fix <strong>for</strong> APAR PQ91101 applied to <strong>DB2</strong> and the fix <strong>for</strong> APAR<br />

PQ94872 applied to <strong>DB2</strong> PE.<br />

Example 4-2 DBM1 Storage Statistics <strong>for</strong> a <strong>DB2</strong> <strong>Version</strong> 8 subsystem<br />

DBM1 AND MVS STORAGE BELOW 2 GB QUANTITY DBM1 AND MVS STORAGE BELOW 2 GB CONTINUED QUANTITY<br />

-------------------------------------------- ------------------ -------------------------------------------- ------------------<br />

TOTAL DBM1 STORAGE BELOW 2 GB (MB) 539.30 24 BIT LOW PRIVATE (MB) 0.21<br />

TOTAL GETMAINED STORAGE (MB) 236.09 24 BIT HIGH PRIVATE (MB) 0.43<br />

VIRTUAL BUFFER POOLS (MB) N/A 31 BIT EXTENDED LOW PRIVATE (MB) 30.45<br />

VIRTUAL POOL CONTROL BLOCKS (MB) N/A 31 BIT EXTENDED HIGH PRIVATE (MB) 553.99<br />

EDM POOL (MB) 234.38 EXTENDED REGION SIZE (MAX) (MB) 1628.00<br />

COMPRESSION DICTIONARY (MB) N/A EXTENDED CSA SIZE (MB) 256.83<br />

CASTOUT BUFFERS (MB) N/A<br />

DATA SPACE LOOKASIDE BUFFER (MB) N/A AVERAGE THREAD FOOTPRINT (MB) 0.46<br />

HIPERPOOL CONTROL BLOCKS (MB) N/A MAX NUMBER OF P<strong>OS</strong>SIBLE THREADS 2377.81<br />

DATA SPACE BP CONTROL BLOCKS (MB) N/A<br />

TOTAL VARIABLE STORAGE (MB) 231.47<br />

TOTAL AGENT LOCAL STORAGE (MB) 195.72<br />

TOTAL AGENT SYSTEM STORAGE (MB) 2.32<br />

NUMBER OF PREFETCH ENGINES 6<br />

NUMBER OF DEFERRED WRITE ENGINES 10<br />

NUMBER OF CASTOUT ENGINES 0<br />

NUMBER OF GBP WRITE ENGINES 0<br />

NUMBER OF P-LOCK/NOTIFY EXIT ENGINES 0<br />

TOTAL AGENT NON-SYSTEM STORAGE (MB) 193.40<br />

TOTAL NUMBER OF ACTIVE USER THREADS 500<br />

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

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

Saved successfully!

Ooh no, something went wrong!