Home > Workload Solutions > Oracle > Guides > Design Guide—Modernize Your Oracle Database Server Platform and Accelerate Deployments > HammerDB test database configuration
We used HammerDB to generate an OLTP that simulates enterprise applications. By generating a significant load on the Oracle infrastructure, our goal was to determine the performance difference between baseline configuration and best practices configuration.
We began the test database environment configuration by creating a test database. We performed the dbca command as the Oracle user to create an Oracle database using the following disk groups:
We used the following main performance related database settings or database limit settings for this HammerDB test in the baseline configuration.
SGA_target | 128GB |
PGA_target | 38GB |
DB_BLOCK_SIZE | 8k |
Processes, sessions, transactions | 640 |
Sessions | 984 |
Transactions | 1082 |
Undo_management, | Auto |
Undo tablespace | UNDOTBS1 |
filesystem_io_options | SETALL |
disk_async_io | TRUE |
db_file_multiblock_read_count | 128 |
db_writer_process | 1 |
redolog file size | 200 MB each |
redolog file block size | 512 |
LOG_CHECKPOINT_INTERVAL | 0 |
LOG_CHECKPOINT_TIMEOUT | 1800 |
log_buffer | 115200K |
redo/ temp files | coarse |
In addition to these database parameters, we maintained the ASM disk group parameter AU Size to the default value of 4MB in the baseline configuration.
The Hammer DB workload configuration is shown in the following table:
Setting Name | Value |
Total transactions per user | 1,000,000 |
Number of warehouses | 10,000 |
Number of virtual users | 80 |
Minutes of ramp up time | 10 |
Minutes of test duration | 50 |
Use all warehouses | Yes |
User delay (ms) | 100 |
Repeat delay (ms) | 100 |
Iterations | 1 |