4 ms·
I don't know why you keep responding by saying it's not a write-back cache. 1. I didn't ever call it a write-back cache and never even hinted at it operating l
by tw04 5y ago
I don't know why you keep responding by saying it's not a write-back cache.
1. I didn't ever call it a write-back cache and never even hinted at it operating like one
2. Write-back caching is only one of many options for write caches
Regardless of both of those points, the SLOG ABSOLUTELY will speed up writes if you have a bursty workload (like the virtual machines he's running) and sync=always enabled.
>A crucial difference is that the ZIL is limited by the available memory regardless (and tunables, by default 5 seconds worth of data), which would not be the case for a write-back cache device.
And yet that point is irrelevant to OPs question of whether or not SLOG was speeding up his writes, which it almost assuredly is doing with the amount of memory and the size of his SLOG device when he is doing sync writes.
- magicalhippo 5y agoFair enough, I should have just called it cache. The point remains though. The ZIL is not meant to be a cache. The SLOG (which is a "ZIL on a separate device") could be viewed as a cache, but it's a cache for the ZIL. Thus being a cache for writes is incidental, not the primary purpose. Certainly, if your workload aligns with those conditions, then you will experience a performance boost. For other workloads it it won't help and for certain workloads it can even be detrimental[1]. [1]: https://www.reddit.com/r/zfs/comments/m6ydfv/performance_effects_of_slog_on_ssd_and_ram_disk/ https://www.reddit.com/r/zfs/comments/m6ydfv/performance_eff...