Manual sizing
The workload was adjusted so that the individual servers have different requirements (100% = 1 CPU fully utilized)
- The web server systems are minimally utilized systems
- The database servers are also considered to be low-utilization systems, which means the load is always less than 90% of one processor
- The two standalone WebSphere® Application
Servers were used to vary the load:
- Triplet 1, the WebSphere guest must not exceed 80% CPU utilization
- Triplet 2 has a WebSphere server with 2 CPUs, and the workload is set so that the CPUs are utilized to approximately 130%
- The workload of the combo servers is set so that the CPUs are utilized to approximately 130% . In both cases the "last" CPU may be idle during the test
Table 1 shows
the sizing settings as configured in our manual sized setup:
The total memory size of all guests in a set is 9,508
MiB. Both sets together are defined with 19,016 MiB.| Set number | Guest name | Function | Number of CPUs | Memory (MiB) |
|---|---|---|---|---|
| 1 | lnweb1 | IBM® HTTP Server | 1 | 342 |
| 1 | lnweb2 | IBM HTTP Server | 1 | 342 |
| 1 | lnwas1 | WebSphere Application Server | 1 | 1600 |
| 1 | lnwas2 | WebSphere Application Server | 2 | 1600 |
| 1 | lnudb1 | DB2® UDB | 1 | 512 |
| 1 | lnudb2 | DB2 UDB | 1 | 512 |
| 1 | lncombo1 | All above | 3 | 2300 |
| 1 | lncombo2 | All above | 3 | 2300 |
| 2 | lnwas3 | WebSphere Application Server | 1 | 1600 |
| 2 | lnwas4 | WebSphere Application Server | 2 | 1600 |
| 2 | lnudb3 | DB2 UDB | 1 | 512 |
| 2 | lnudb4 | DB2 UDB | 1 | 512 |
| 2 | lncombo3 | All above | 3 | 2300 |
| 2 | lncombo4 | All above | 3 | 2300 |
| 2 | lnweb3 | IBM HTTP Server | 1 | 342 |
| 2 | lnweb4 | IBM HTTP Server | 1 | 342 |