All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Tracy Reed <treed@ultraviolet.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] poor mysqldump performance
Date: Fri, 24 Feb 2012 09:18:58 +0100	[thread overview]
Message-ID: <4F4747F2.7000001@redhat.com> (raw)
In-Reply-To: <20120223235949.GK22456@tracyreed.org>

On 02/24/2012 12:59 AM, Tracy Reed wrote:
> On Fri, Feb 24, 2012 at 12:10:43AM +0100, Arno Wagner spake thusly:
>> I notice that you are using a really, really old kernel.
>> 2.6.18 is from end of 2006 or so. There were some
>> performance issues with the dm-layer, they might just
>> still be in this old version.

RHEL5 uses old dmcrypt code which is stable but has known
limitations.
The last change in RHEL was backporting suport for XTS mode.

Backporting of some performance changes is almost impossible
(if it easy I perhaps tried that long time ago).

Also please note that this is exactly where RHEL customer
requests helps - and there were no such requests.
So other things get priority.

So if you are using CentOS my advice is simple - try to upgrade
to CentOS6 and test it. It should be in some aspect better but still
database performance over dmcrypt can have problems.

Setting nr_request will not help btw, this is different problem.

Milan

  reply	other threads:[~2012-02-24  8:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 22:23 [dm-crypt] poor mysqldump performance Tracy Reed
2012-02-23 23:10 ` Arno Wagner
2012-02-23 23:59   ` Tracy Reed
2012-02-24  8:18     ` Milan Broz [this message]
2012-02-24 19:07       ` Tracy Reed
2012-02-24 20:05         ` Arno Wagner
2012-02-24 22:30           ` Tracy Reed
2012-02-25  2:13             ` Arno Wagner
2012-02-24  1:29 ` Alasdair G Kergon
2012-02-24  2:55   ` Tracy Reed

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=4F4747F2.7000001@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=treed@ultraviolet.org \
    /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.