From: "shmick@riseup.net" <shmick@riseup.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] benchmark, kernel, libgcrypt, comparisons
Date: Thu, 30 Jan 2014 01:22:27 +1100 [thread overview]
Message-ID: <52E90EA3.2020404@riseup.net> (raw)
i came across a text file benchmark i did with the 2nd latest cryptsetup
and thought id see how 1.6.3 would look
i have different kernel and libgcrpyt versions since 1.6.2 as well and
it was said on the gnupg list when libgcrypt 1.6.0 came out there were
some speed improvements
what would likely be the main source of speed increases - kernel or
libgcrypt ?
serpent decryption is vastly faster, twofish in general but seems AES isn't
$ cryptsetup benchmark
1.6.2
libgcrypt 1.5.3
kernel 3.2.0-58
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 337814 iterations per second
PBKDF2-sha256 175229 iterations per second
PBKDF2-sha512 111455 iterations per second
PBKDF2-ripemd160 255500 iterations per second
PBKDF2-whirlpool 142935 iterations per second
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 150.0 MiB/s 181.1 MiB/s
serpent-cbc 128b 56.7 MiB/s 61.2 MiB/s
twofish-cbc 128b 140.0 MiB/s 192.8 MiB/s
aes-cbc 256b 119.5 MiB/s 137.3 MiB/s
serpent-cbc 256b 56.7 MiB/s 60.9 MiB/s
twofish-cbc 256b 140.4 MiB/s 192.8 MiB/s
aes-xts 256b 172.0 MiB/s 176.8 MiB/s
serpent-xts 256b 58.2 MiB/s 60.7 MiB/s
twofish-xts 256b 132.5 MiB/s 138.3 MiB/s
aes-xts 512b 132.0 MiB/s 134.3 MiB/s
serpent-xts 512b 58.9 MiB/s 61.2 MiB/s
twofish-xts 512b 132.0 MiB/s 137.9 MiB/s
$ cryptsetup benchmark
1.6.3
libgcrypt 1.6.0
kernel 3.11.0-15
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 680010 iterations per second
PBKDF2-sha256 468114 iterations per second
PBKDF2-sha512 315076 iterations per second
PBKDF2-ripemd160 458293 iterations per second
PBKDF2-whirlpool 154748 iterations per second
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 150.2 MiB/s 180.4 MiB/s
serpent-cbc 128b 52.3 MiB/s 228.2 MiB/s
twofish-cbc 128b 138.4 MiB/s 190.4 MiB/s
aes-cbc 256b 117.5 MiB/s 136.0 MiB/s
serpent-cbc 256b 56.9 MiB/s 237.8 MiB/s
twofish-cbc 256b 139.9 MiB/s 190.2 MiB/s
aes-xts 256b 171.3 MiB/s 176.6 MiB/s
serpent-xts 256b 207.1 MiB/s 215.0 MiB/s
twofish-xts 256b 175.8 MiB/s 175.8 MiB/s
aes-xts 512b 131.4 MiB/s 134.1 MiB/s
serpent-xts 512b 209.4 MiB/s 214.8 MiB/s
twofish-xts 512b 175.7 MiB/s 175.7 MiB/s
next reply other threads:[~2014-01-29 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:22 shmick [this message]
2014-01-29 14:59 ` [dm-crypt] benchmark, kernel, libgcrypt, comparisons Milan Broz
2014-01-29 15:52 ` shmick
2014-01-30 22:10 ` Matthias Schniedermeyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E90EA3.2020404@riseup.net \
--to=shmick@riseup.net \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox