summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorJakob Unterwurzacher2021-09-14 18:47:41 +0200
committerJakob Unterwurzacher2021-09-14 18:58:22 +0200
commit2d0ba24ecab375f276f024bc014faad9a7ef169c (patch)
tree53d2c219c7e5135561c1e4a1fd7e4d56777d77ee /README.md
parent61e37b2439f0b8a7c16458e73cb57c7428fe61f2 (diff)
-speed: print cpu model
When somebody posts "gocryptfs -speed" results, they are most helpful together with the CPU model. Add the cpu model to the output. Example: $ ./gocryptfs -speed gocryptfs v2.2.0-beta1-5-g52b0444-dirty; go-fuse v2.1.1-0.20210825171523-3ab5d95a30ae; 2021-09-14 go1.17.1 linux/amd64 cpu: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz; with AES acceleration AES-GCM-256-OpenSSL 862.79 MB/s AES-GCM-256-Go 997.71 MB/s (selected in auto mode) AES-SIV-512-Go 159.58 MB/s XChaCha20-Poly1305-OpenSSL 729.65 MB/s XChaCha20-Poly1305-Go 843.97 MB/s (selected in auto mode)
Diffstat (limited to 'README.md')
-rw-r--r--README.md13
1 files changed, 7 insertions, 6 deletions
diff --git a/README.md b/README.md
index e4ea9a7..69a3416 100644
--- a/README.md
+++ b/README.md
@@ -168,12 +168,13 @@ Example for a CPU with AES-NI:
```
$ ./gocryptfs -speed
-gocryptfs v2.2.0-beta1-4-gcdbc48f; go-fuse v2.1.1-0.20210825171523-3ab5d95a30ae; 2021-09-14 go1.17.1 linux/amd64
-AES-GCM-256-OpenSSL 868.09 MB/s
-AES-GCM-256-Go 997.97 MB/s (selected in auto mode)
-AES-SIV-512-Go 160.72 MB/s
-XChaCha20-Poly1305-OpenSSL 722.14 MB/s
-XChaCha20-Poly1305-Go 841.89 MB/s (selected in auto mode)
+gocryptfs v2.2.0-beta1-5-g52b0444-dirty; go-fuse v2.1.1-0.20210825171523-3ab5d95a30ae; 2021-09-14 go1.17.1 linux/amd64
+cpu: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz; with AES acceleration
+AES-GCM-256-OpenSSL 862.79 MB/s
+AES-GCM-256-Go 997.71 MB/s (selected in auto mode)
+AES-SIV-512-Go 159.58 MB/s
+XChaCha20-Poly1305-OpenSSL 729.65 MB/s
+XChaCha20-Poly1305-Go 843.97 MB/s (selected in auto mode)
```
You can run `./benchmark.bash` to run gocryptfs' canonical set of