White Papers

21 Sizing and Best Practices for Online Transaction Processing Applications with Oracle 11g R2 using Dell PS Series | BP1003
The peak load was around 10,234 IOPS compared to 17,000 IOPS in the previous test configuration.
The entire capacity of the SSDs was saturated when the space utilization was increased to 2 TB. The
simulated I/O was completely random with no locality of data access. Consequently, the SSDs had to wait for
I/O activity to complete on the 10K SAS drives and the maximum IOPS delivered was decreased to around
10,000 IOPS.
5.3.3 ORION (4 TB array capacity utilization, 100% random I/O and no data locality)
The ORION and Vdbench tests described in sections 5.3.1 and 5.3.2 were run using 8K I/O block size and a
read-write ratio of 70/30. This represented a typical TPC-C like workload.
TPC-E is a highly read-intensive workload typically represented by 90% read and 10% write I/O. To determine
the baseline performance, the I/O ratio was fixed to 92/8 read/write with 8K I/O block size in this ORION test.
Also, 4 TB of the total array capacity was used while running this test.
This I/O ratio was fixed based on the I/O ratio observed when the actual TPC-E transactions were run on the
Oracle RAC database. Refer to section 7.3 for more details.