> The snapshots are all made to tmpfs so hopefully does not measure delays introduced by the network or disk activity. This by itself would make an interesting

> The snapshots are all made to tmpfs so hopefully does not measure delays introduced by the network or disk activity. This by itself would make an interesting benchmark. In the previous company that I worked for, there was a customer who used Veeam Backup to a disk backed by Ceph, in an 8+3 erasure-coded pool. And they were complaining to us about disk space overuse by Ceph and poor performance. We traced that to the fact that Veeam uses 128KB transfer size (too small) and excessive fsyncs.