MD5 and SHA-1 were designed to be cryptographically secure hashing algorithms. While fairly fast for small files, comparing large numbers of large files can become prohibitively slow, which is what leads me to request an implementation of a faster, non-cryptographic hash algorithm meant for file comparison. The fastest I've found is xxHash3.
Considering that the collision risk of xxHash3 is acceptably low even in combinatorial situations (where each hash is compared to all other hashes), the risk of collision in a one-to-one scenario such as file comparison should be negligible (~3.14 collisions per billion comparisons).
I'm not a programmer so I'm not sure how difficult it would be to include in rclone, but the github page seems well-maintained and the developer seems to be actively supporting it, so that seems to be a good sign.
What about with rclone check --download or rclone move -c from a service that doesn't include hashing? Those are two cases where the file would have to be hashed on both ends
so mega does not perform a checksum and/or save a checksum as metadata on upload?
for each upload, you are forced to re-download all the data to perform a checksum?
if you do not mind, why did you choose mega over other cloud providers?
and using a rclone mount would not be a good solution.
need to use fuse compatibility layer.
the slow download speed is the problem, not the fast checksum calculated by rclone
I agree with your explanation though; disk/network speed will almost always be a limiting factor or close to it. The only case where xxhash stands out is when comparison occurs during RAM or if downloading doesn't happen until a hash is complete, but I bet rclone is probably pretty good at downloading and hashing together, so this should probably be a low priority.