53b7c17261
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:55:13 +02:00
bfc8d47747
doc: add performance numbers for 1.3-27
2017-05-25 21:30:58 +02:00
61502f9b94
benchmark: add md5sum read performance benchmark
2017-03-18 16:23:33 +01:00
cb5426e8ee
performance.txt: add numbers for current gocryptfs master and encfs v1.9.1
2016-11-26 12:46:58 +01:00
10884603d8
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
40420cb4cd
Update performance.txt for v1.1 release
2016-10-09 23:19:08 +02:00
f030123ab5
Add performance numbers for v0.11
2016-06-08 00:32:40 +02:00
776c734f43
Update readme.md and performance.txt for v0.9
2016-04-10 23:01:00 +02:00
e42e46c97c
Add v0.9-rc2 performance numbers
2016-04-10 12:04:50 +02:00
4a1768a314
Automate standard performance tests
2016-01-23 19:33:03 +01:00
8432382244
Update README for v0.7.2
2016-01-19 23:01:21 +01:00
04abad5e84
Update performance data for v0.7
2015-12-20 15:39:40 +01:00
9419e7ae85
Update README + docs for v0.6 release
2015-12-08 16:41:45 +01:00
fc23aba65b
performance.txt: link to linux-3.0.tar.gz
2015-12-04 22:45:16 +01:00
accf8144ca
Move docs to Documentation folder
2015-12-01 18:19:24 +01:00
Jakob Unterwurzacher