hardcoresushi/libgocryptfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity
53b7c17261
libgocryptfs/Documentation/performance.txt

37 lines
1.6 KiB
Plaintext
Raw Normal View History

OpenDir performance: Read DirIV once and reuse it for all names Formerly, we called decryptPath for every name. That resulted in a directory walk that reads in all diriv files on the way. Massive improvement for RM and LS (check performance.txt for details) VERSION UNTAR RM LS v0.4 48 5 1.5 v0.5-rc1 56 19 7 v0.5-rc1-1 54 9 4.1 <---- THIS VERSION
2015-11-29 19:57:48 +01:00
All test performed on tmpfs, /tmp/a mounted on /tmp/b.
benchmark.bash: double write length Writing 1000 128KB blocks takes only 1 second and yielded inconsistent results. With 2000, things look saner.
2016-11-26 12:36:55 +01:00
The untar test uses https://cdn.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.gz .
Update performance data for v0.7
2015-12-20 15:39:40 +01:00
The archive is placed on tmpfs as well.
OpenDir performance: Read DirIV once and reuse it for all names Formerly, we called decryptPath for every name. That resulted in a directory walk that reads in all diriv files on the way. Massive improvement for RM and LS (check performance.txt for details) VERSION UNTAR RM LS v0.4 48 5 1.5 v0.5-rc1 56 19 7 v0.5-rc1-1 54 9 4.1 <---- THIS VERSION
2015-11-29 19:57:48 +01:00
benchmark.bash: double write length Writing 1000 128KB blocks takes only 1 second and yielded inconsistent results. With 2000, things look saner.
2016-11-26 12:36:55 +01:00
WRITE: dd if=/dev/zero of=zero bs=128K count=2000
UNTAR: time tar xzf ../linux-3.0.tar.gz
benchmark: add md5sum read performance benchmark
2017-03-18 16:23:33 +01:00
MD5: time md5sum --quiet -c linux-3.0.md5sums
Update performance data for v0.7
2015-12-20 15:39:40 +01:00
LS: time ls -lR linux-3.0 > /dev/null
RM: time rm -Rf linux-3.0
OpenDir performance: Read DirIV once and reuse it for all names Formerly, we called decryptPath for every name. That resulted in a directory walk that reads in all diriv files on the way. Massive improvement for RM and LS (check performance.txt for details) VERSION UNTAR RM LS v0.4 48 5 1.5 v0.5-rc1 56 19 7 v0.5-rc1-1 54 9 4.1 <---- THIS VERSION
2015-11-29 19:57:48 +01:00
performance.txt: add numbers for current gocryptfs master and encfs v1.9.1
2016-11-26 12:46:58 +01:00
(or just run benchmark.bash)
Update performance.txt for v1.1 release
2016-10-09 23:19:08 +02:00
benchmark: add md5sum read performance benchmark
2017-03-18 16:23:33 +01:00
VERSION WRITE UNTAR MD5 LS RM
v0.4 48 1.5 5
v0.5-rc1 56 7 19
v0.5-rc1-1 54 4.1 9
v0.5-rc1-2 45 1.7 3.4
v0.6 47 1.8 4.3
v0.7 43 1.7 4.3
v0.7.2 26 1.8 4.3
v0.8 23 1.8 4.3
v0.9-rc2 94 24 1.8 4.5
v0.9 94 24 1.8 4.5
v0.11 104 22 1.7 4.5
v1.1 104 20 1.5 3.4 (go1.7.1)
v1.1.1-34 112 22 1.5 3.6 (go1.7.3)
v1.2.1-33 112 21 12 1.6 4.4 (go1.8)
v1.2.1-33
-serialize_reads 116 21 39 1.5 4.4
doc: add performance numbers for 1.3-27
2017-05-25 21:30:43 +02:00
v1.3-27 113 20 11 1.4 4.2
Don't cap GOMAXPROCS at 4. Before Go 1.5, GOMAXPROCS defaulted to 1, hence it made sense to unconditionally increase it to 4. But since Go 1.5, GOMAXPROCS defaults to the number of cores, so don't keep it from increasing above 4. Also, update the performance numbers.
2017-06-01 20:53:03 +02:00
v1.3-53-gf44902a 119 19 12 1.6 4.1
performance.txt: add numbers for current gocryptfs master and encfs v1.9.1
2016-11-26 12:46:58 +01:00
benchmark: add md5sum read performance benchmark
2017-03-18 16:23:33 +01:00
Results for EncFS for comparison (benchmark.bash -encfs):
performance.txt: add numbers for current gocryptfs master and encfs v1.9.1
2016-11-26 12:46:58 +01:00
benchmark: add md5sum read performance benchmark
2017-03-18 16:23:33 +01:00
VERSION WRITE UNTAR MD5 LS RM
encfs v1.9.1 95 20 8 2.8 3.8
Reference in New Issue Copy Permalink