Demystifying OpenZFS 2.0
EDIT: There is a now an incorrect response to this post of mine stating that I forgot to mention the ZIL SLOG -- but the poster doesn't understand how the ZIL SLOG actually works unfortunately. :(I applaud OpenZFS for these major improvements, but its performance is not competitive with some of the commercial offerings, even if OpenZFS is a more easily administered solution.The main issue with OpenZFS performance is its write speed.While OpenZFS has excellent read caching via ARC and L2ARC, it doesn't enable NVMe write caching nor does it allow for automatic tiered storage pools (which can have NVMe paired with HDDs.)This means that large writes, those which exceed the available RAM, will drop down to the HDD write speed quite quickly instead of achieving wire speed.  Which means I get write speeds of 300 MBps versus 10 GBps wirespeed.The solutions competitors have implemented are:- SSD read-write caching, usually using mirrored NVMe drives to ensure redundancy.- SSD tiering, which is including your SSDs in your storage pool.  Frequently accessed data is moved onto the SSDs while infrequently accessed data is moved to the HDDs.Without these features, my QNAP (configured with SSD tiering) kicks the pants off of ZFS on writes that do not fit into memory.References:[1] QNAP Tiering: https://www.qnap.com/solution/qtier/en-us/[2] QNAP SSD Read-Write Caching: https://www.qnap.com/solution/ssd-cache/en/[3] Synology SSD Read-Write Caching: https://kb.synology.com/en-my/DSM/help/DSM/StorageManager/ge...