From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS & TrueCrypt - Speed Test
Date: Wed, 27 Jul 2011 19:18:24 -0400 [thread overview]
Message-ID: <4E309CC0.6010706@gmail.com> (raw)
Hello everyone,
Inspired by this old blog post:
http://movingparts.net/2007/10/26/truecrypt-versus-luks-speed-test/
...I decided to perform some tests on my Fedora 14 box. This is not a
pro benchmark so be warned :)
Common Facts for both tests:
- source & destination filesystems were ext4
- destination is an external USB drive
- source data size is 143GB (a folder with lots of files & directories,
small & large files, regular data...)
- rsync was used to perform the actual copy
- I'm using an "encrypted partition " (against an encrypted file)
- I did a test first with TrueCrypt and then with LUKS
- Between the above tests, I shut down the machine (to flush filesystem
cache).
- my system kernel: 2.6.35.13-92.fc14.i686
### TrueCrypt Results ####
I used AES-256 (XTS operation mode), hash algorithm: ripemd-160 and the
package was realcrypt-7.0a-1.fc14.i686
Output of time command after rsync finished:
real 105m22.211s
user 28m10.471s
sys 41m35.319s
### DM-Crypt LUKS Results ###
I used the defaults: AES-256 (CBC), sha1 for header hashing and the
package cryptsetup-luks-1.1.3-1.fc14.i686
Output of time command after rsync finished:
real 108m55.291s
user 28m6.534s
sys 42m53.400s
As you can see, there's almost a 4 minute difference. I was expecting
LUKS to be faster (as dm-crypt is a kernel module) and TrueCrypt runs
mainly in user space isn't it? Do you think the cipher operation modes
(XTS vs CBC) played a role in this difference? Have any of you performed
a similar test?
Regards,
Jorge
next reply other threads:[~2011-07-27 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 23:18 Jorge Fábregas [this message]
2011-07-28 5:11 ` [dm-crypt] LUKS & TrueCrypt - Speed Test Arno Wagner
2011-07-28 13:07 ` Jorge Fábregas
2011-07-28 7:40 ` Milan Broz
2011-07-28 13:20 ` Jorge Fábregas
2011-07-28 23:58 ` Jorge Fábregas
2011-07-29 5:20 ` Arno Wagner
2011-07-29 9:52 ` Roscoe
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=4E309CC0.6010706@gmail.com \
--to=jorge.fabregas@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.