@@ -67,9 +67,9 @@ nested drive.
67
67
directory to this local gocryptfs drive, and then syncs this gocryptfs drive
68
68
to a remote server.
69
69
- Doing this is relatively efficient compared to the first solution.
70
- (On my laptop, with about 20,000 files, it takes about 20 seconds to stat
71
- all files. Then syncing to to a remote server with SFTP takes about 40
72
- seconds to stat all files).
70
+ (On my laptop with Intel Core i7-8565U , with about 20,000 files, it takes
71
+ about 20 seconds to stat all files. Then syncing to to a remote server with
72
+ SFTP takes about 40 seconds to stat all files).
73
73
- Huge plus in this regard is no longer having to deal with FUSE on Windows.
74
74
- Major disadvantage to this approach is one must have enough storage for
75
75
both the entire gocryptfs drive and the plaintext files that we actually want.
@@ -99,8 +99,9 @@ introduces a simple LRU path lookup cache for frequently accessed paths.
99
99
100
100
With these simple cache mechanisms in place, Gocrypt SFTP outperforms as well
101
101
as or even better than the second approach described in
102
- [ Motivations] ( #motivations ) . On my laptop, with about 20,000 files, it takes
103
- under 1 minute to stat (in plaintext) all files in the remote gocryptfs drive.
102
+ [ Motivations] ( #motivations ) . On my laptop with Intel Core i7-8565U, with
103
+ about 20,000 files, it takes under 1 minute to stat (in plaintext) all files
104
+ in the remote gocryptfs drive.
104
105
105
106
106
107
0 commit comments