| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-06-26 | doc: update performance.txt | Jakob Unterwurzacher | |
| 2021-06-05 | doc: add benchmark for v2.0, reformat table | Jakob Unterwurzacher | |
| 2021-04-07 | Doc: update performance.txt | Jakob Unterwurzacher | |
| 2021-04-03 | performance.txt: add dirfd caching results | Jakob Unterwurzacher | |
| Also, add v2.0-beta2-16-geaca820. I bisected the ls performance regression to this commit. | |||
| 2020-11-10 | performance.txt: add v2.0-beta1-9 results | Jakob Unterwurzacher | |
| 2020-10-18 | fusefronted: reject GETXATTR "security.capability" | Jakob Unterwurzacher | |
| Unless we are mounted with -suid, we can reject these requests, and gain back some lost speed. Closes https://github.com/rfjakob/gocryptfs/issues/515 | |||
| 2020-10-16 | performance.txt: add gocryptfs v1.8.0 results | Jakob Unterwurzacher | |
| 2020-10-16 | Update performance.txt with gocryptfs v2.0-beta1 result | Jakob Unterwurzacher | |
| As expected, we are slow. Fd caching will be implemented later. | |||
| 2020-05-03 | Documentation: update performance.txt | Jakob Unterwurzacher | |
| Bisecting shows that the performance drop is caused by this commit: commit ca9e912a28b901387e1dbb85f6c531119f2d5ef2 (refs/bisect/bad) Author: Jakob Unterwurzacher <jakobunt@gmail.com> Date: Sat Feb 29 19:58:08 2020 +0100 fusefrontend: drop xattr user namespace restriction | |||
| 2020-02-15 | performance.txt: update result for governor = performance | Jakob Unterwurzacher | |
| Also add big signs where the cpu has changed, as the results are not comparable when the cpu is different. Also update encfs results. | |||
| 2019-10-13 | Update performance.txt | Jakob Unterwurzacher | |
| 2019-01-04 | Update performance.txt | Jakob Unterwurzacher | |
| 2018-08-18 | Update README for v1.6 release | Jakob Unterwurzacher | |
| 2018-06-12 | Update README and MANPAGE for v1.5v1.5 | Jakob Unterwurzacher | |
| Also update the performance numbers. I see some slowdown, reason is not yet clear, but nothing to block the release. | |||
| 2017-09-10 | performance.txt: specify READ tests | Jakob Unterwurzacher | |
| 2017-09-03 | performance.txt: update for v1.4.1 latest commits, and kernel update | Jakob Unterwurzacher | |
| $ uname -a Linux brikett 4.12.5-300.fc26.x86_64 #1 SMP Mon Aug 7 15:27:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux | |||
| 2017-08-15 | Update performance.txt for Linux kernel upgrade | Jakob Unterwurzacher | |
| For some reason, writing became a lot faster in Linux 4.11 (scheduler improvements?). | |||
| 2017-08-15 | Update performance.txt for to Getdents change | Jakob Unterwurzacher | |
| 2017-08-15 | docs: label "ENV CHANGE" column | Jakob Unterwurzacher | |
| 2017-07-01 | Update performance.txt with new results | Jakob Unterwurzacher | |
| Massive speed boost for streaming reads. | |||
| 2017-06-29 | Update performance.txt with new numbers | Jakob Unterwurzacher | |
| 2017-06-29 | Update performance.txt with new numbers | Jakob Unterwurzacher | |
| 2017-06-20 | Update performance numbers | Jakob Unterwurzacher | |
| 2017-06-11 | Add performance numbers for v1.3-69-ge52594d | Jakob Unterwurzacher | |
| 2017-06-11 | Add performance numbers for last change | Jakob Unterwurzacher | |
| Slight streaming write improvement. | |||
| 2017-06-09 | performance.txt: add numbers for latest change | Jakob Unterwurzacher | |
| Also, get rid of the half-empty line. | |||
| 2017-06-01 | Don't cap GOMAXPROCS at 4. | Jakob Unterwurzacher | |
| 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-05-25 | doc: add performance numbers for 1.3-27 | Jakob Unterwurzacher | |
| 2017-03-18 | benchmark: add md5sum read performance benchmark | Jakob Unterwurzacher | |
| 2016-11-26 | performance.txt: add numbers for current gocryptfs master and encfs v1.9.1 | Jakob Unterwurzacher | |
| 2016-11-26 | benchmark.bash: double write length | Jakob Unterwurzacher | |
| Writing 1000 128KB blocks takes only 1 second and yielded inconsistent results. With 2000, things look saner. | |||
| 2016-10-09 | Update performance.txt for v1.1 release | Jakob Unterwurzacher | |
| 2016-06-08 | Add performance numbers for v0.11 | Jakob Unterwurzacher | |
| 2016-04-10 | Update readme.md and performance.txt for v0.9 | Jakob Unterwurzacher | |
| 2016-04-10 | Add v0.9-rc2 performance numbers | Jakob Unterwurzacher | |
| 2016-01-23 | Automate standard performance tests | Jakob Unterwurzacher | |
| 2016-01-19 | Update README for v0.7.2v0.7.2 | Jakob Unterwurzacher | |
| 2015-12-20 | Update performance data for v0.7 | Jakob Unterwurzacher | |
| 2015-12-08 | Update README + docs for v0.6 releasev0.6 | Jakob Unterwurzacher | |
| 2015-12-04 | performance.txt: link to linux-3.0.tar.gz | Jakob Unterwurzacher | |
| 2015-12-01 | Move docs to Documentation folder | Jakob Unterwurzacher | |
 |
index : gocryptfs | |
| Mirror of gocryptfs source code on Github | https://github.com/rfjakob/gocryptfs |
| summaryrefslogtreecommitdiff |