Page 1
Sizing and Best Practices for Online Transaction Processing Applications with Oracle 11g R2 using Dell PS Series Dell EMC Engineering March 2017 A Dell EMC Technical White Paper
Page 2
Revisions Date Description December 2013 Initial release March 2017 Updated for Dell EMC branding; consolidated two best practices documents (BP1003 and BP1069) Acknowledgements This best practice whi...
Page 3
Table of contents Revisions................................................................................................................................................................................
Page 4
6.3 TPC-E I/O with increased write I/O ................................................................................................................... 35 6.4 TPC-E on PS6110XS .......................
Page 5
Executive summary Online transaction processing (OLTP) applications — ranging from web-based e-commerce sites, to accounting systems, to customer support programs — are at the heart of today’s busines...
Page 6
1 Introduction Different types of database applications have varying performance and capacity needs. Understanding the models for common database application workloads can be useful in predicting the ...
Page 7
1.3 Terminology The following terms are used throughout this document: AMM: The Oracle Automatic Memory Management (AMM) feature automates and simplifies the memory- tuning configuration tasks by allo...
Page 8
2 OLTP applications with PS Series arrays OLTP database applications are optimal for managing rapidly changing data. These applications typically have many users who are performing transactions simult...
Page 9
3 Solution infrastructure The test system used to conduct ORION, Vdbench, and TPC-C/TPC-E testing for this paper is shown in this section. 3.1 Physical system test configuration The logical test confi...
Page 10
The logical test configuration diagram for OLTP database application tests (TPC-E) using Quest Benchmark Factory is shown in Figure 2. TPC-E test configuration — LAN and i SCSI SAN connectivity 3.2 St...
Page 11
3.3 Database layout The PS Series arrays were placed in different pools, and Oracle ASM disks were configured using the ASM disk layout described as follows. DB1DATA: Database files; temporary table s...
Page 12
Figure 3 shows the containment model and relationships between the PS Series pool and volumes, and the Oracle ASM disk groups and disks. PS Series volume and Oracle ASM disk configuration 12 Sizing an...
Page 13
4 Test methodology A series of I/O simulations were conducted using ORION to understand the performance characteristics of the PS Series XV, S, and XS hybrid storage arrays. The ORION tool was install...
Page 14
4.2 Test criteria The test criteria used for the study includes: The storage array disk access latencies (read and write) remain below 20 ms per volume. Database server CPU utilization remains bel...
Page 15
5 I/O profiling study The ORION tool uses the Oracle I/O software stack to generate simulated I/O workloads without having to create an Oracle database, load the application, and simulate users. ORION...
Page 16
Key findings from the test results are summarized as follows: As expected, average IOPS increased with the queue depth. The PS6010XV array in a RAID 10 configuration produced approximately 4,000 I...
Page 17
Key findings from the test results are summarized as follows: For 100% read I/O with an 8K block size, the PS6010S array sustained a maximum of approximately 34,000 IOPS. For 70/30 read/write I/O ...
Page 18
The results collected from these tests are illustrated in sections 5.3.1 to 5.3.4. Additional I/O simulation tests were run to evaluate Oracle ASM benefits and also to determine the volume configurati...
Page 19
The SAN HQ chart in Figure 7 shows that each SSD drive was producing more than 5,300 IOPS during peak I/O activity. Disk IOPS activity reported by SAN HQ ( 1 TB capacity utilization and no data locali...
Page 20
5.3.2 ORION (2 TB array capacity utilization, 100% random I/O and no data locality) In this test, 4 x 500 GB volumes were used to run the ORION test. The total capacity utilization was 2 TB. Because t...
Page 21
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 sim...
Page 22
This test on the array produced approximately 7,167 IOPS with less than 12ms latency on the storage array as shown in the SAN HQ chart in Figure 9. IOPS and latency reported by SAN HQ (4 TB capacity u...
Page 23
5.3.4 Vdbench (2 TB array capacity utilization, 100% random I/O and 20% data locality) Applications such as Oracle OLTP databases typically contain both infrequently accessed and highly dynamic data w...
Page 24
The SAN HQ chart in Figure 10 shows the gradual increase in IOPS from 7,000 to 12,000 over the test time span due to the automatic tiering feature of PS6110XS arrays. Test start: Steady state: 7,000 I...
Page 25
The total capacity utilization on the array was kept constant at 2 TB and only the volume configuration was modified as shown in Table 3. Test parameters: Volume configuration studies Configuration pa...
Page 26
The results displayed in Figure 11 confirm higher performance when there are eight or more volumes. Increasing the number of volumes beyond eight did not result in any significant increase in IOPS. IO...
Page 27
Slightly higher IOPS (4,300 compared to 4,200) were observed with the ASM configuration. The IOPS numbers maintained the generally accepted disk latency limit of 20 ms (for both read and write latenci...
Page 28
6 OLTP performance studies using TPC-E like workload The ORION and Vdbench test results described in section 5 helped in determining the baseline performance of a typical Oracle OLTP database on PS Se...
Page 29
Test parameters: Oracle memory management study Configuration parameters PS Series SAN 1 x PS6010XV: 16 x 300GB 15K SAS disks with dual 2-port 10Gb E controllers 14 SAS disks configured as RAID 10...
Page 30
A 9% increase in IOPS was observed when the memory was increased to 48 GB from the default setting of 38 GB. At the same time, the performance dropped when the memory was increased to a larger value s...
Page 31
6.2 TPC-E (array capacity utilization study) The performance from the storage array differed based on the capacity utilization as illustrated by the ORION test results in sections 5.3.1 to 5.3.3. The ...
Page 32
IOPS, latency, and disk IOPS reported by SAN HQ (TPC-E I/O with 1 TB array capacity utilization) 32 Sizing and Best Practices for Online Transaction Processing Applications with Oracle 11g R2 using De...
Page 33
Also, as you can see from the IOPS activity on the disks, complete I/O activity was handled by the SSDs and there was no I/O activity on the 10K SAS drives. This is because the array capacity utilizat...
Page 34
IOPS, latency, and disk IOPS reported by SAN HQ (TPC-E I/O with 4 TB array capacity utilization) 34 Sizing and Best Practices for Online Transaction Processing Applications with Oracle 11g R2 using De...
Page 35
As seen in the SAN HQ chart in Figure 14, I/O activity was observed on both the SSD and 10K SAS drives. A peak IOPS of 19,000 was observed compared to almost 27,000 as described in section 6.2.1 (1 TB...
Page 36
TPC-E transactions were simulated using this modified transaction mix to determine the performance from a PS6110XS array when exposed to heavy write-intensive I/O workload, which is a worst-case scena...
Page 37
Oracle AWR reports were captured while running these tests and constantly monitored for any RAC or database related bottlenecks. The top 10 events of the AWR report are shown in Figure 17. Top 10 even...
Page 38
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 s...
Page 39
7 Best practice recommendations 7.1 Storage A configuration with more small volumes is preferred over a low number of large volumes for better performance and simpler management of OLTP databases. It ...
Page 40
7.4 Oracle database application 7.4.1 Database volume layout The following are database volume layout best practices: Oracle recommends using ASM for simplified administration and optimal I/O balanc...