From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Poor performane (idle cpu)
Date: Mon, 8 Feb 2010 02:50:28 +0100 [thread overview]
Message-ID: <20100208015028.GA1408@tansi.org> (raw)
In-Reply-To: <20100208011654.GA4927@southpole.se>
On Mon, Feb 08, 2010 at 02:16:54AM +0100, Jakob Sandgren wrote:
> Hi,
>
> I'm using dm-crypt for several mappings with a hardware raid backend.
> Using a raw read from the raid device (e.g sda) gives ~250MB/s
>
> But when I read from an encrypted mapping, I just get ~70MB/s. That
> should be fine if I at least have the kcryptd process using a core at
> 100%, but that is not the case. Three of my four cores is 99% idle and
> one core is 50% idle (aprox.).
Which means your core is too slow to support the full 250MB/s
speed.
> I have recently upgraded my hardware from an older quadcore system
> (AMD) to a new Core I7 (860) and expected improved performance and
> when I did not get that, then did I do some more investegation and
> found out above. I have also read posts from others having the same
> problems, but no explanation.
I suspect as the core can support only about 140MB/s encryption
speed, the accesses get broken. It is well possible that
if your array would only give 120MB/s it would still have
that rate encrypted.
> Anyone who has an explanation for this or a hint if one could
> "tune" anything to get better performance?
You may try to encrypt the individual disks and do the
RAID on top of the decrypted disks. That way you should
have more cores participate in the crypto. The problem
with this is of course that this requires the flexibility
of software RAID and hardware RAID cannot do it.
You can also try larger stripe sizes, but that should
make only a minor difference.
You can also try slow your RAID down to something
like 120MB/s in ordert o stay within what a single
core can decrypt.
Just a note on multicore speed: It is often better to have
fewer faster cores than more slower ones. Your problem
is an exapmle for that.
Arno
> Output from "cryptsetup status":
>
> /dev/mapper//dev/mapper/shared1 is active:
> cipher: aes-cbc-essiv:sha256
> keysize: 128 bits
> device: /dev/mapper/areca_0_1-shared1_raw
> offset: 1032 sectors
> size: 3145726968 sectors
> mode: read/write
>
>
> Best Regards,
> Jakob
>
>
> --
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-02-08 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 1:16 [dm-crypt] Poor performane (idle cpu) Jakob Sandgren
2010-02-08 1:50 ` Arno Wagner [this message]
2010-02-08 23:54 ` Jakob Sandgren
2010-02-09 0:28 ` Arno Wagner
2010-02-09 14:48 ` [dm-crypt] Poor performane (idle cpu) [SOLVED; problem with "pv"] Jakob Sandgren
2010-02-09 16:14 ` Arno Wagner
2010-02-09 16:16 ` M Thomas Frederiksen
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=20100208015028.GA1408@tansi.org \
--to=arno@wagner.name \
--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.