I’m using 1.4.6 linux with FUSE. I’m rsync’ing local files into the vault. The sync and encryption process for my backup has improved since 1.4.0, but is still too slow (right now, three photo jpegs per minute). I’ve done some digging in the source code of cryptomator and cryptolib. It appears that extensive locking may be the culprit.
If I rsync a tree starting at directory ./a and the jpegs are in nesting level 4 (i.e. ./a/b/c/d is a dir that contains the files) it is much slower that rsyncing directory ./d directly. I looks like as if locks are acquired for a, then a/b, then a/b/c, then a/b/c/d, then the file is compared, then all the locks are lifted vice versa, and then all the locks are acquired again for the next file in directory d. Thus, rsyncing whole trees is slow.
The locking code is spread a bit around between cryptolib and cryptomator. Without docs not easy to analyse. Any hints on how to tackle this issue? I’m happy to help if someone points me in theright direction …