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 09:07:22 -0400 [thread overview]
Message-ID: <4E315F0A.4050109@gmail.com> (raw)
In-Reply-To: <20110728051117.GB5441@tansi.org>
On 07/28/2011 01:11 AM, Arno Wagner wrote:
> There is an old gemran egineering saying:
>
> "wer mist mist mist"
>
> (along the lines of "Those who measure measure crap")
> I think it applies here.
Hello Amo,
I warned everyone that this wasn't a pro test :) At least, I laid down
the specifics involved.
> Real-time is tricky. It does not reflect effort invested. If you
> look at the sys itime, you see that the crypto-effort is only about
> 90 seconds more. Even that is pretty much below the measurement
> error.
I agree here. I shouldn't have paid much attention to real time.
Nonetheless I'm still curious about the little difference...
> Very likely the differences are due to storage differences
> and do not show crypto-speed differences.
I used the same external drive for both tests.
> I suggest you run both tests at least 3 times and make sure
> your storage is significantly faster than the crypto, e.g.
> by doing this between RAM disks or SSD storage. Also a complex
> disk access patterhn like rsync is not suitable as it may
> have complex interactions with caching and buffering.
I didn't want to go with sequential & random read/writes (with different
block sizes etc) as I wanted a rough test out of the very same tool I
use every day (rsync) with the same data on the same disk. I understand
the crypto involved (CPU-wise) is much faster than the slow I/O of my
external drive but that's what I have. Regarding repeating the test, I
totally agree with that.
Thanks for the input.
Regards,
Jorge
next prev parent reply other threads:[~2011-07-28 13:07 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 [this message]
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=4E315F0A.4050109@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.