Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2017-08-16T16:33:00+00:00 2017-08-16T16:33:00+00:00 Jakob Unterwurzacher 2017-08-16T16:33:00+00:00 urn:sha1:312ea32bb70abb93be315d0b7c442d5c4ae571d9 The benchmark that supported the decision for 512-byte prefetching previously lived outside the repo. Let's add it where it belongs so it cannot get lost. 2017-06-09T20:05:14+00:00 Jakob Unterwurzacher 2017-06-09T19:52:26+00:00 urn:sha1:80516ed3351477793eec882508969b6b29b69b0a On my machine, reading 512-byte blocks from /dev/urandom (same via getentropy syscall) is a lot faster in terms of throughput: Blocksize Throughput 16 28.18 MB/s 512 83.75 MB/s For a single-threaded streaming write, this drops the CPU usage of nonceGenerator.Get to almost 1/3: flat flat% sum% cum cum% Before 0 0% 95.08% 0.35s 2.92% github.com/rfjakob/gocryptfs/internal/cryptocore.(*nonceGenerator).Get After 0.01s 0.092% 92.34% 0.13s 1.20% github.com/rfjakob/gocryptfs/internal/cryptocore.(*nonceGenerator).Get This change makes the nonce reading single-threaded, which may hurt massively-parallel writes.