All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Wendler <ml@philippwendler.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Strance performance problems
Date: Thu, 27 Oct 2011 20:34:59 +0200	[thread overview]
Message-ID: <4EA9A453.8040103@philippwendler.de> (raw)
In-Reply-To: <4EA98296.40601@morlix.de>

Hi,

Am 27.10.2011 18:11, schrieb morlix:

> Which brings ~5MB/s write performance on the encrypted raid 5.
> 
> What i find strange is the huge avgqu-sz.
> 
> 
> I have no clue what the reason for this poor write performance could be.
> 
> Thanks for every hint to resolve this issue.

I have the same problem[1][2].
One other person with the same problem contacted me after this.
Apparently for him a smaller chunk size of the raid 5 (64k instead of
512k) solved the problem, but I have not been able to test this yet. I
would be very interested to know whether this helps for you.

Greetings, Philipp

[1] http://www.saout.de/pipermail/dm-crypt/2011-July/001773.html
[2] http://superuser.com/q/305716/84630

  reply	other threads:[~2011-10-27 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 16:11 [dm-crypt] Strance performance problems morlix
2011-10-27 18:34 ` Philipp Wendler [this message]
2011-10-29 18:00   ` [dm-crypt] Strange " morlix

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=4EA9A453.8040103@philippwendler.de \
    --to=ml@philippwendler.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.