Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

Measurement results
Table 11-2 provides the resulting GPFS data sizes after BI Accelerator index
creation for our 5 TB, 15 TB, and 25 TB databases. Note that although the final
space used in GPFS is much smaller than configured, more space is actually
used for storing BI Accelerator temporary objects. Additionally, more than three
times the space is required if backups or other activities are planned. Most
importantly, this study shows that from 0.6 TB to 1.3 TB of fact table data per
hour can be indexed to the BI Accelerator, which is quite impressive.
Table 11-2 Index creation results: throughput, duration, and space
Database volume size
and blade resources
The CPU usage for the database server on System z was rather light during BI
Accelerator index creation. The average CPU rates at steady state were 11.84%,
25.00%, and 26.72% for 5 TB, 15 TB, and 25 TB, respectively.
The next three figures show the CPU utilization of SAP BI on System p and SAP
BI Accelerator on blades for the three BI Accelerator index creation
measurements taken at steady state. The average high load utilization on the
charts refers to the average CPU utilization at steady state.
244 Best Practices for SAP BI using DB2 9 for z/OS
Throughput
(terabytes/hr
Duration
(hh:mm:ss)
GPFS size
5 TB index creation 27 blades 0.6 6:40:30 300 GB
15 TB index creation 81 blades 1.1 11:07:07 800 GB
25 TB index creation 135 blades 1.3 15:04:29 1.1 TB