All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: linux-raid@vger.kernel.org
Subject: Re: Performance Testing MD-RAID10 with 1 failed drive
Date: Fri, 21 Oct 2022 10:15:42 +0200	[thread overview]
Message-ID: <6c31fc94-b70e-88c5-205a-efff32baf594@plouf.fr.eu.org> (raw)
In-Reply-To: <20221021001405.2uapizqtsj3wxptb@bitfolk.com>

Le 21/10/2022 à 02:14, Andy Smith a écrit :
> 
> On Thu, Oct 20, 2022 at 12:13:19PM +0530, Umang Agarwalla wrote:
>> But what I am trying to understand is, how to benchmark the
>> performance hit in such a condition.
> 
> Perhaps you could use dm-dust to make an unreliable block device
> from a real device?

That seems uselessly complicated to me. What about this ?

- benchmark the array in the clean state
- fail and remove a drive
- benchmark the array in the degraded state
- add a new drive and start the resync
- benchmark the array in the resync state

  reply	other threads:[~2022-10-21  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 19:30 Performance Testing MD-RAID10 with 1 failed drive Umang Agarwalla
2022-10-19 21:00 ` Reindl Harald
2022-10-19 21:12   ` Umang Agarwalla
2022-10-19 21:25   ` Wols Lists
2022-10-19 22:56     ` Reindl Harald
2022-10-19 23:23     ` Roger Heflin
2022-10-20  6:43       ` Umang Agarwalla
2022-10-21  0:14         ` Andy Smith
2022-10-21  8:15           ` Pascal Hambourg [this message]
2022-10-21 10:51             ` Andy Smith
2022-10-21 11:51               ` Roger Heflin
2022-10-21 15:24                 ` Andy Smith
2022-10-21 16:01                   ` Umang Agarwalla
2022-10-21 16:53                   ` Roger Heflin

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=6c31fc94-b70e-88c5-205a-efff32baf594@plouf.fr.eu.org \
    --to=pascal@plouf.fr.eu.org \
    --cc=linux-raid@vger.kernel.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.