Skip to main content
NetApp Knowledge Base

Will high delays from ONTAP processing layer impact Oracle Redo workload performance?

Last Updated:

Applies to



Oracle Redo logs workload work on a cycle and bursy by nature. The bursty WRITE workload may overwhelm the processing layer and exhibit wait-time in WAFL However, it is totally normal; Redo logging can write many MB at a time. 

An Oracle Redo log writes is a single thread of variable sized IO's and can stuff a lot of IO into ONTAP in a burst. The burst often looks like a severe latency problem, but it is rarely an actual problem.

Oracle does very efficient IO, often with low concurrency. Just make sure all of the instructions in Technical Report 3633 with respect to kernel parameters, mount options and ONTAP options are precisely followed and implemented.  Misconfiguration of those parameters will damage sequential IO performance more than other IO.

Additional Information

Use the following Knowledge Base to analyze Oracle performance using Automatic Workload Repository (AWR)


NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device