From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] performance of dm-crypt devices?
Date: Wed, 22 Aug 2007 13:06:49 +0200 [thread overview]
Message-ID: <46CC18C9.400@wpkg.org> (raw)
I just set up an encrypted LUKS device using the information on
http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedDeviceUsingLUKS
There was a suggestion there, which prompted me to check the performance:
If you wish, use /sbin/hdparm to benchmark. However my benchmarks on
an AMD Athlon 3200 indicate no great difference between an encrypted
and a normal unencrypted partition.
First, I set read-ahead to the same value on both devices (original LVM
device, and the crypted one):
# blockdev --setra 16384 /dev/mapper/crypttest
# blockdev --setra 16384 /dev/mapper/san1-test
Next, hdparm test:
# hdparm -t mapper/crypttest mapper/san1-test
mapper/crypttest:
Timing buffered disk reads: 116 MB in 3.01 seconds = 38.54 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate
ioctl for device
/dev/san1/file1-swap:
Timing buffered disk reads: 304 MB in 3.12 seconds = 97.46 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate
ioctl for device
So, this quick test suggests that with a crypted device, I get about 40%
performance of the original LVM volume?
My setup is hardware RAID-10, and a dual core 3 GHz Xeon.
Is it normal? I would say yes, as both cores use 100% CPU when I do
intensive reads from an encrypted volume.
However, this seems to contradict with "However my benchmarks on an AMD
Athlon 3200 indicate no great difference between an encrypted and a
normal unencrypted partition".
I used aes-cbc-essiv:sha256 cipher.
Perhaps, I should use something lighter?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2007-08-22 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 11:06 Tomasz Chmielewski [this message]
2007-08-22 11:26 ` [linux-lvm] performance of dm-crypt devices? Tomasz Chmielewski
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=46CC18C9.400@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-lvm@redhat.com \
/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.