All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.com>
To: dm-devel@redhat.com
Subject: Clustered RAID1 performance
Date: Thu, 30 May 2013 11:59:55 +0200	[thread overview]
Message-ID: <20130530095955.GE11926@suse.de> (raw)

Hi all,

we see a significant performance hit when mirroring is used for a cLVM2
LV.

That's clearly due to the performance overhead of bouncing to user-space
(and worse, to the network) for locking etc.

I wonder if consideration has been given to how this could be improved?
Using the in-kernel DLM and holding locks for regions the local node
writes to for longer, exclusive locks while noone is reading,
parallelizing the resync ...? How is the long-term perspective for this
given the dm-raid/md raid stuff?

Before we go drafting I wanted to ask for ideas that are already
floating around ;-) Anyone working on this?


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

             reply	other threads:[~2013-05-30  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  9:59 Lars Marowsky-Bree [this message]
2013-05-31 15:58 ` Clustered RAID1 performance Brassow Jonathan
2013-06-03 20:45   ` Lars Marowsky-Bree

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=20130530095955.GE11926@suse.de \
    --to=lmb@suse.com \
    --cc=dm-devel@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.