You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that transferring files on the same disk, but between different directories, are very slow and not at all what I'd expect from my NVMe disk (and I know that the port and cable aren't the issue here). I might be talking out of my ass here, but I'm assuming this is because cryfs has to write to the database, but it is not limited by disk read/write speed but rather CPU-bound on a single thread. Therefore, I believe, cryfs read/write operations are limited to the speed at which your CPU can write on a single thread, and perhaps bottlenecks caused by the programming language itself. Please correct me if anything I've said is wrong, I'm just making assumptions here.
P.S. is there a more discussion-oriented forum for cryfs somewhere? If not, creating a discourse forum or at least a subreddit would go a long way to get more attention to this project and hopefully have it audited at some point.
The text was updated successfully, but these errors were encountered:
Have you made any progress with this issue?
I am experiencing this as well, even to an extend that the transfer will crash and I cannot unmount the drive due to it still being busy.
Transfer from a different drive seems to be without issues.
@0xalivecow I haven't used cryfs in a while, but I never fixed it. I also experience the same issue with restic and borgbackup. I'm pretty sure it's bottlenecked by the app itself, but I have no detailed explanation beyond that. Even when transferring files to the same PCIe 4.0 disk, speeds are abysmal. Issue occurs on different machines, different OS's, different disks. Can't have anything to do with my hardware.
I have noticed that transferring files on the same disk, but between different directories, are very slow and not at all what I'd expect from my NVMe disk (and I know that the port and cable aren't the issue here). I might be talking out of my ass here, but I'm assuming this is because cryfs has to write to the database, but it is not limited by disk read/write speed but rather CPU-bound on a single thread. Therefore, I believe, cryfs read/write operations are limited to the speed at which your CPU can write on a single thread, and perhaps bottlenecks caused by the programming language itself. Please correct me if anything I've said is wrong, I'm just making assumptions here.
P.S. is there a more discussion-oriented forum for cryfs somewhere? If not, creating a discourse forum or at least a subreddit would go a long way to get more attention to this project and hopefully have it audited at some point.
The text was updated successfully, but these errors were encountered: