4 ms·
Let's see how this works out. It's probably better and more stable than btrfs but this is not complicated... ZFS on Linux had issues with ARC (especially fast
by nisa 11y ago
Let's see how this works out. It's probably better and more stable than btrfs but this is not complicated...
ZFS on Linux had issues with ARC (especially fast reclaim) and some deadlocks and AFAIK cgroups are not really supported - e.g. blkio throttling does not work.
Would be great is they got this ironed out but I would be wary. Still great news!
- AstralStorm 11y agoAdditional problem is that in-kernel latencies of both btrfs and ZFS are on the high end. Essentially a show stopper for professional audio work and maybe some kinds of video streaming. Trying to completely escape disk IO in those uses is very limiting. A comparable solution using LVM and/or mdraid with ext4 on top has much better latency behavior. Sorry for no benches for you, but feel free to run a quick check using latencytop and ftrace. Phoronix has some performance comparisons if you want them.
- semi-extrinsic 11y ago> Essentially a show stopper for professional audio work (...). Trying to completely escape disk IO in those uses is very limiting. Could you expand on that? I mean, an hour of mono uncompressed 192 kHz/24bit audio is almost exactly 2 GB. Compared to professional audio equipment, 128 GB of RAM isn't very expensive ( < $2000), and that would let you keep 64 one-hour maximum-def tracks in memory. Why do you need to read from the disk with any frequency?