There are almost 2,000 Azure customers running Oracle database workloads on Azure VMs, and that number is growing rapidly all the time. Running Oracle on Azure is not the first idea to occur to many people, but it should be, as there are several types of VMs appropriate for Oracle workloads within Azure, as well as multiple choices for storage, ranging from inexpensive to high-performance. Overall, Oracle performs very well in Azure, and there are several great features in Azure to make running Oracle even easier, such as Azure VM Backup (i.e. topic for another post).
One of the most common configurations is running one or more Oracle databases on an Azure VM with premium SSD managed disk. When attaching managed disk to a VM, one has the option of enabling ReadOnly host-caching or ReadWrite host-caching for the managed disk device.
What is host-caching? Essentially it is locally-attached SSD on the physical host underlying the virtual machines, and it is documented HERE. When the VM is allocated to a physical host and running, locally-attached SSD is used with a simple LRU1 caching algorithm for I/O between the VM and the virtualized network-attached managed disk device. ReadOnly host-caching caches only read I/O from the VM to the managed disk device, while ReadWrite host-caching caches both read and write I/O operations from the VM to the managed disk.
Please note that ReadWrite host-caching is intended either as the default setting for the VM OsDisk, or for data disks using filesystems with barrier functionality enabled, as cited HERE. It is not a great idea to use ReadWrite host-caching with Oracle database files, because of possible data-integrity issues resulting from lost writes should the VM crash.
But the rest of this article pertains to the use of ReadOnly host-caching for managed disk for Oracle database workloads.
If the Oracle online redo log files are isolated from other database files and reside on their own ReadOnly host-cached disk, then…
Generally each block in online redo log files are written once and then read only once. ReadOnly host-caching ignores the write altogether and does the work to cache the single read, as it is designed. However, if there is never second, third, or subsequent read, then the maintenance of the cache chains and the cache buffers performed at the first read is entirely wasted. Worse still, this happens with every single block written to the online redo log files, over and over again; the cache is constantly manipulated, consuming compute resources, but to no benefit. I don’t believe that this activity slows I/O operations for the online redo log files significantly, but simply increases the consumption of compute resources which could otherwise be used productively, which of course means that the overall system is capable of accomplishing less work.
If the Oracle online redo log files are not isolated and reside on the same ReadOnly host-cached disk as other database files…
This is where actual performance decreases can result. Oracle datafiles, tempfiles, controlfiles, BFILEs, files for external tables, block change tracking files, and Flashback log files do in fact use ReadOnly host-caching appropriately, with numerous reads of the same block after each write, not to mention the buffer caching within the RDBMS itself. If Oracle online redo log files activity is mixed into the same workload as the Oracle datafiles, tempfiles, controlfiles, etc, then ReadOnly host-caching is forced to cache the online redo log files as well, even though there is zero benefit, along with the rest of the database files. As a result, blocks stay in the cache for less time due to the constant rollover of buffers enforced by the sequential online redo log files workload, making the ReadOnly cache less effective for all files, and causing more “overhead” as pages/blocks needlessly “flushed” from the cache by the sequentially-written redo need to re-acquired. This is the scenario where the ReadOnly host-caching is noticeably less effective, and the average I/O latency does not improve.
Also, if using the D_v3 or E_v3 or M series of VMs…
ReadOnly host-caching actually provides slower I/O throughput on these VM instance types than uncached I/O, which is impressively fixed with the Dds_v4 and Eds_v4 series. For example, this table (below) summarizes from the documentation pages the differences in IOPS and I/O throughput limits of the Standard_E32s_v3 series and the Standard_E32ds_v4 instance types, as illustration…
|Size||vCPU||Memory (GB)||Max cached and temp storage IOPS||Max cached and temp storage throughput (MBPS)||Max uncached disk IOPS||Max uncached disk throughput (MBps)|
As you can see, I/O throughput for cached storage is lower than the I/O throughput for uncached storage for v3, while a more intuitive result is apparent for v4.
The same is true for other size instance types, of course; I just didn’t display them.
In summary, if you wish to reap the expected benefits of ReadOnly host-caching, do not use D_v3 or E_v3 instance or anything in the M-series instance types.
So in summary, I think these are good rules for using Azure VM host-caching with Oracle database workloads…
- Don’t use ReadWrite host-caching with Oracle database files
- Isolate the transaction logs from other database files to separate managed disk devices and disable host-caching
- Use ReadOnly host-caching for all other Oracle database files
- Do not use the D_v3, E_v3, or M-series VMs because host-caching and ephemeral SSD is slow compared to Dds_v4 and Eds_v4 series VMs