MAA - Oracle 10gR2 Redo Transport and Network Best Practices
MAA - Oracle 10gR2 Redo Transport and Network Best Practices
MAA - Oracle 10gR2 Redo Transport and Network Best Practices
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Maximum Availability Architecture<br />
MB/<br />
sec<br />
140<br />
120<br />
100<br />
Figure 5: <strong>Redo</strong> Apply Performance with Active Data Guard<br />
80<br />
60<br />
40<br />
20<br />
0<br />
<strong>Redo</strong> Apply Performance with<br />
Active Data Guard<br />
48<br />
47<br />
45<br />
116<br />
112 111<br />
OLTP Batch<br />
Mounted<br />
Read Only<br />
Read Only<br />
RAC<br />
read-only st<strong>and</strong>by database, as is the case with Active Data Guard. Testing included<br />
examining the effects of having multiple st<strong>and</strong>by instances open read-only while<br />
<strong>Redo</strong> Apply was being performed by a single st<strong>and</strong>by instance.<br />
Role Transition Performance<br />
The time required to complete role transitions using an active st<strong>and</strong>by database is<br />
similar to that required for a physical st<strong>and</strong>by database that is not open read-only.<br />
Please see My <strong>Oracle</strong> Support Note 843803.1 for additional information.<br />
Application Scalability<br />
Application scalability was tested using Swingbench, an <strong>Oracle</strong> load-generation<br />
tool. Within Swingbench, the <strong>MAA</strong> tests used the Order Entry application that<br />
consists of five transaction types that are typical in any order-entry application:<br />
Creating a Customer, Browsing Products, Placing Orders, Processing Orders <strong>and</strong><br />
Reviewing Orders. The I/O size for this workload is small (generally, it is the size<br />
of the tablespace blocksize, which in this case is 4K). Swingbench connects to the<br />
database using thin JDBC <strong>and</strong> uses all <strong>MAA</strong> client configuration best practices.<br />
The read/write workload consists of creating new customers, placing orders, <strong>and</strong><br />
processing orders. The read-only workload consists of catalog <strong>and</strong> order browsing.<br />
In the initial testing state, the primary database has both read/write <strong>and</strong> read-only<br />
workloads running that are connected through separate services as described under<br />
‘Managing Initial Client Connections’ section. The read/write workload has 50<br />
users connected, while the read-only workload has 100 users connected. With both<br />
workloads running on the primary database, the production host is operating at<br />
100% capacity. Figure 6 shows the transactions per second on the primary<br />
database.<br />
<strong>Oracle</strong> Active Data Guard: <strong>Oracle</strong> Data Guard 11g Page 18
Change language