Run Oracle OLTP workloads in HP-UX vPars and Integrity VM v6.1.5

• Automatic Memory Mode enabled

• Archive Mode disabled

• Three redo log groups, each 4 GB in size

• Data files created with bigfile option to allow growth beyond 32 GB

• init.ora Parameters

– db_block_size=8192 (8 KB Database Block Size)

– memory_target=38912M (38 GB Memory Target, it is advisable to have memory target size

around or less than 60 percent of the guest memory)

Workload generator configuration

Swingbench is a workload generator for Oracle databases. Swingbench has an OLTP workload and a DSS workload. For

this set of measurements, the OLTP workload was used as most of the customers indicated that they are predominantly

interested in running OLTP workloads in their production environment. And for this reason, this white paper

demonstrates the comparative analysis of OLTP workload run on native, vPar guests, and Integrity VM guests

environments.

The Swingbench OLTP workload used in this analysis is called SOE. It comprises five transactions that are run repeatedly.

The results shown in this white paper are based on Swingbench v2.3.

The default workload mix used by Swingbench v2.3 induces a large amount of row lock contention. While this might be a

valid workload, severe row lock contention is not typical of most production environments, at least not for extended

periods of time. The SOE workload profile mix was modified in Swingbench v2.4 to reduce the row lock contention

inherent in the v2.3 profile. It may result in a higher transaction rate and read/write concurrency.

The database was populated using Datagenerator (part of the Swingbench suite). Datagenerator creates a database file

of a specified size and an index file roughly twice the size of the database. So, the overall dataset is three times the size

of the database file itself.

For each run, the following Swingbench parameters were used:

• Minimum think time: 1 millisecond

• Maximum think time: 2 milliseconds

• Duration of run: 30 minutes

• AWR snapshots were collected during last 10 minutes of 30 minutes run