All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS & TrueCrypt - Speed Test
Date: Thu, 28 Jul 2011 19:58:58 -0400	[thread overview]
Message-ID: <4E31F7C2.4050305@gmail.com> (raw)
In-Reply-To: <4E309CC0.6010706@gmail.com>

On 07/27/2011 07:18 PM, Jorge Fábregas wrote:
> I decided to perform some tests on my Fedora 14 box.   This is not a
> pro benchmark so be warned :)

Hi everyone,

I performed the tests again (twice for each test) but this time I
formatted the LUKS partition using:

cryptsetup luksFormat -c aes-xts-plain -s 256 -h ripemd160 /dev/sdd1

...so that I was more _similar_ to the TrueCrypt setup.  Also, between
each test I run:

echo 3 > /proc/sys/vm/drop_caches

Here are the new results for the same payload (143 GB of data):

### TRUECRYPT ####

1st round:
real	105m39.547s
user	28m17.667s
sys	42m25.300s


2nd round:
real	105m40.271s
user	28m21.893s
sys	42m19.672s


### LUKS ###

1st round:
real	104m33.901s
user	27m41.362s
sys	41m0.339s


2nd round:
real	104m44.913s
user	27m42.364s
sys	40m57.655s


Now as you may see, LUKS is roughly around 1 minute ahead (sytem-time)
compared to TrueCrypt.  It appears the change in cipher operation mode
definitely affected the results (thing I should have done on the first
place).

Cheers and thank your for the feedback!
Jorge

  parent reply	other threads:[~2011-07-28 23:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 23:18 [dm-crypt] LUKS & TrueCrypt - Speed Test Jorge Fábregas
2011-07-28  5:11 ` 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 [this message]
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=4E31F7C2.4050305@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.