As it mentioned earlier that ZFS appliance is best suited to OLAP workload but you can use ZFS Appliance for Non-critical OLTP workload. By nature, Online transaction processing (OLTP) workloads tend to go after a small number of rows per IO request. Imagine a busy OLTP system where thousands of random IO’s going after a small amount of data, will require shorter response time to maintain and achieve healthy response time. That means you should use utilize ZFS read & write flash SSD’s to get reasonable performance for your OLTP applications. Similar to OLAP database workload, it is recommended to use Bigfile tablespace and Oracle Direct NFS. But unlike OLAP workload its best to use Advance Row Compression to optimize IO response time and memory utilization.
|Recommended OLAP Database Layout on ZFS Storage|
|Oracle Files||Record Size||Sync Write Bias||Read Cache||Comp
|Example Share Name|
|Datafiles||128K||throughput||do not use cache devices||LZ4||data|
|Temp||128K||latency||do not use cache devices||LZ4||temp|
|Archive Logs||1M||throughput||do not use cache devices||LZ4||archive|
|RMAN Backup||1M||throughput||do not use cache devices||LZ4||backup|
Again, let’s look into rest of the recommendation of mapping different databases files to their recommended location and record sizes. Data files, temp files, and archive logs can be placed ton ZFS share with respective record sizes 32K, 128K and 1M. Similarly, it’s best practices to place online redo logs and control files in the default Fast Recovery Area (FRA) on the preconfigured Exadata ASM diskgroup.