White Papers
38 Sizing and Best Practices for Online Transaction Processing Applications with Oracle 11g R2 using Dell PS Series | BP1003
When the capacity utilization was increased to 4 TB, the IOPS changed from 25,675 to 19,000 (see section
6.2.2). This is because the entire data set could not be stored within the SSDs and had to be spread across
all of the SSDs and 10K SAS drives. The SSDs also had to wait for the I/O activity to complete on the 10K
SAS drives.
The PS6110XS arrays performed well, even with the modified heavy write-intensive TPC-E-style I/O
operations as described in section 6.3. The PS6110XS arrays produced more than 8,700 IOPS with very
heavy write operations introduced as part of TPC-E-modified workload.
Figure 18 compares the performance numbers produced by the ORION I/O performance numbers (see
section 5.3.3) and the TPC-E-style workload with write-intensive I/O transactions simulated using Quest
Benchmark Factory (see section 6.3).
Increase in IOPS: ORION or TPC-E
ORION is a synthetic tool that provides an estimate of Oracle OLTP performance without actually installing an
Oracle database, whereas TPC-E provides estimates of Oracle OLTP performance by executing the workload
on actual Oracle databases.
Typically in database applications, there are specific areas on the disks such as REDO logs which are
accessed more frequently than the other database objects. These frequently accessed objects usually need
higher performance than other database objects.
Figure 18 shows more than a 21% increase in IOPS with the TPC-E workload. This is due to TPC-E reflecting
the typical database I/O characteristics where a specific locality is being accessed frequently. On the other
hand, the ORION tool could not simulate this behavior.
When a specific locality is accessed frequently, the PS6110XS internal tiering mechanism identifies the hot
pages and then moves them to the SSD tier as demonstrated in section 5.3.4. These results clearly show how
the internal data tiering mechanism of the PS6110XS hybrid array helps in Oracle OLTP database
performance improvements while cost-effectively satisfying the capacity requirements simultaneously.
ORION
TPC-E
IOPS
Increase in IOPS: ORION or TPC-E
TPC-E
21%