All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Birkholz <dennis.birkholz@rwth-aachen.de>
To: dm-crypt@saout.de
Subject: [dm-crypt] Poor write performance on software raid with 512k chunk size
Date: Sun, 26 Feb 2012 13:29:31 +0100	[thread overview]
Message-ID: <4F4A25AB.7040003@rwth-aachen.de> (raw)

Hello together,

i experienced severe performance problems when using a crypt mapping on
a software raid 5 with 512k chunk size. Without a crypt mapping the
write speed was ~100M/sec, with the crypt mapping it had only ~20M/sec.
After is rebuild the raid on the same disks using 64k chunk size, the
write performance with the crypt mapping is now ~90M/sec. I am using a
self compiled 3.2.6 vanilla kernel on a debian squeeze with an AMD
Phenom(tm) II X4 955 processor.

For now reducing the chunk size solved the problem for me but 512k chunk
size was chosen as the default by mdadm so it would be nice to find the
reason for this performance bottleneck.

Greets,
Dennis

             reply	other threads:[~2012-02-26 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26 12:29 Dennis Birkholz [this message]
2012-02-26 13:37 ` [dm-crypt] Poor write performance on software raid with 512k chunk size Alasdair G Kergon
2012-02-26 16:45   ` Dennis Birkholz

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=4F4A25AB.7040003@rwth-aachen.de \
    --to=dennis.birkholz@rwth-aachen.de \
    --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.