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 > Hardware design and operating system usage
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
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.
While running batch jobs, backups, or loading large amounts of data, the CPU might be driven to high percentages such as to 80 to 100% to maximize throughput.
DB2 supports the following processor configurations:
- Uni-Processor
- A single system that contains only one single CPU
- SMP (symmetric multiprocessor)
- A single system that can contain multiple CPUs. Scalability is limited to the CPU sockets on the motherboard.
- MPP (massively parallel processors)
- A system with multiple nodes connected over a high speed link. Each node has its own CPUs. Adding new nodes achieves scalability.
- Inefficient data access methods cause high CPU utilization and are major problems for database system. Regular database maintenance is an important factor.
- Paging and swapping require CPU time. Consider this factor while planning your memory requirements.
Parent topic:
Hardware design and operating system usage