Running Oracle OLTP workloads in HP Integrity VM 4.3

10
Results
Several different benchmark tests were run using varying Oracle database instance sizes and varying numbers of
Swingbench users. Table 1 below contains the results from the different Swingbench runs conducted during this effort.
The results in table 1 are merely an example of Integrity VM performance achieved during an internal benchmarking
effort. Your results will vary based on configuration and workload.
The columns in the table are as follows:
1. Test #: Uniquely identify each test configuration
2. DB size: Size of the Oracle DB instance, including the primary DB file and the index file
3. SB users: The number of Swingbench users used during the run
4. Disk utilization: The resulting disk utilization as reported by HP GlancePlus software during the run
5. CPU utilization (native): CPU utilization during the physical server runs as reported by Glance Plus
6. CPU utilization (VM): CPU utilization seen during the VM runs as reported by Glance Plus
7. VM TPS delta: The calculated delta between the TPS numbers achieved in the native and VM benchmark runs as
reported in the respective Oracle AWR reports
Table 1. Oracle/Swingbench benchmark results
Test # DB size
SB
users
Disk
utilization
CPU
utilization
(Native)
CPU
utilization
(VM)
VM TPS
Delta
1 56 GB 100 5% 84% 91% 17%
2 70 GB 100 20% 82% 90% 16%
3 85 GB 100 40% 77% 89% 17%
4 70 GB 50 17% 45% 57% 2.4%
Interpreting the results
Looking at the data in the above table, several conclusions can be made.
• Tests 1, 2, and 3 show that running reasonably heavy Oracle workloads in a Integrity VM, with varying amounts of
disk and CPU utilization, yields a TPS delta between 16–17 percent.
• Test 4 shows that an Integrity VM is very capable of running a medium or busy Oracle workload and generating
TPS numbers close to that of a native system.
• As CPU and disk I/O rates approach 100 percent utilization, a greater gap occurs between native and
Integrity VM throughput. It is therefore recommended to run the Integrity VM at less than 100 percent CPU
and I/O utilization.