Re:ZFS, BTRFS, XFS, EXT4 and LVM with KVM – A Storage Perfor...
by josefbacik on Monday May 23, 2016 @09:10AM
(#11753587)
We have to look up the physical extent in the extent reference tree, so the cost is independent of the number of snapshots and more a function of the fragmentation of the extent tree. The metadata is all cached of course, but fragmentation means you are likely to not find the entries in cache.
The other aspect that I haven't talked about is our fsync performance is kind of shit compared to other fs'es. Now this does get better in the nocow case but it's still pretty heavy and needs optimization.
Seems like the expense of checking could be largely removed with clever enough metadata caching, which probably noone has had time to implement.