White Papers

29 Sizing and Best Practices for Online Transaction Processing Applications with Oracle 11g R2 using Dell PS Series | BP1003
Test parameters: Oracle memory management study
Configuration parameters
PS Series SAN
1 x PS6010XV:
 16 x 300GB 15K SAS disks with dual 2-port 10GbE controllers
 14 SAS disks configured as RAID 10, two hot spares
 Controller firmware version: 5.0.0.0 (R122845)
1 x PS6010S:
 16 x 100GB SSD disks with dual 2-port 10GbE controllers
 14 SSDs configured as RAID 10, with two hot spares
 Controller firmware version: 5.0.0.0 (R122845)
1 x PS6110XS:
 7 x 400GB SSDs and 17 x 600GB 10K SAS drives
 RAID 6 Accelerated
 Hosting the database files and REDO logs
1 x PS6110E:
 24 x 2 TB SATA drives as RAID 50
 Hosting the ARCH logs and flash recovery area
Test configuration details
Test configuration #1
AMM (MEMORY_TARGET = 38GB)
Test configuration #2
AMM (MEMORY_TARGET = 48GB)
Test configuration #3
AMM (MEMORY_TARGET = 64GB)
Database workload parameters
Database
2-node RAC running on two R720 servers
User transactions
TPC-E from Benchmark Factory for Databases
Test duration
5 hours
Database size
~900GB (including tables, indexes)
By default, Oracle will set the MEMORY_TARGET value to 40% of the total memory available on the server.
In the test configuration, each node (R720 server) had 96GB of memory. The first test assigned 38 GB of
memory to Oracle. Later, more tests were run with different memory settings (38 GB, 48 GB, and 64 GB) as
shown in Table 5 to determine the configuration which produces optimal performance.