Which is not really a problem in backup scenario: backing things up is a background process, so if it goes slow it does not matter much. (except initial backup, but if you have a lot of data – you can do initial backup over s3) but when you need to access data – it will be fast.
Hmmm. Would not this mean that all chunks are 64? if max is equal to average, then min must be equal to it too.
I think setting average to 32MiB should provide a good balance. It still keeps the chunk size variable, which is good for heterogeneous content, and it’s still almost an order of magnitude (8x) larger than the default (4MiB)
There are scenarios where fixed chunk size is actually prefferend – backing up virtual disks is one example. In fact the vertical backup by the same developer is using fixed block size, because its best suited of this type of content
