IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Performance tuning > Tivoli Data Warehouse > Relational database design and performance tuning for DB2 Database servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Hardware design and operating system usage
For any database system, a number of common areas must be addressed and sized appropriately to support your application workload. This section covers common and platform-specific hardware and operating system components and explains main considerations for hardware design and operating system usage.
It does not include detailed calculations for capacity planning purposes.
Key factors for hardware design and operating system usage include memory, CPU, I/O and network considerations.
- Memory
Understanding how DB2 organizes memory helps you tune memory use for good performance. Many configuration parameters affect memory usage. Some parameters might affect memory on the server, some on the client, and some on the server and the client. Furthermore, memory is allocated and de-allocated at different times and from different areas of the system.
- CPU
CPU utilization should be about 70 to 80% of the total CPU time. Lower utilization means that the CPU can cope better with peak workloads. Workloads between 85% to 90% result in queuing delays for CPU resources, which affect response times. CPU utilization above 90% usually causes unacceptable response times.
- I/O
- Network
After a system is implemented, the network should be monitored to ensure that its bandwidth is not being consumed more than 50%.
Parent topic:
Relational database design and performance tuning for DB2 Database servers