public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: David Mansfield <lkml@dm.cobite.com>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.59mm5, raid1 resync speed regression.
Date: Sat, 25 Jan 2003 03:55:58 +1100	[thread overview]
Message-ID: <3E31701E.4020101@cyberone.com.au> (raw)
In-Reply-To: Pine.LNX.4.44.0301241141540.32240-100000@admin

David Mansfield wrote:

>Hi Andrew, list,
>
>I'm booting 2.5.59mm5 to run a database workload benchmark that I've been
>running against various kernels.  I'll post those results if they are
>interesting later, but I did notice that the raid1 resync is proceeding at
>half the speed (at best) that it usually does (vs. 2.5.59 that is).
>
>It currently at about 4-8 mb/sec (and falling as resync progresses),
>usually at 12-15 mb/sec.
>
>System is SMP 2xPIII 866mhz, 2GB ram, raid1 is two 15k U160 (running only
>an Ultra speed :-( because the onboard controller sucks) SCSI disks, same
>channel on aic7xxx.
>
>Kernel is 2.5.59-mm5 compiled with gcc version 2.96 20000731 (Red Hat 
>Linux 7.3 2.96-112)
>
>David
>
Thanks for the report. Please do post any results you get.

What disk workload exactly does a RAID1 resync consist of?

Nick


  reply	other threads:[~2003-01-24 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 16:48 2.5.59mm5, raid1 resync speed regression David Mansfield
2003-01-24 16:55 ` Nick Piggin [this message]
2003-01-24 18:18   ` David Mansfield
2003-01-24 18:41     ` Nick Piggin
2003-01-24 22:34       ` 2.5.59mm5 database 'benchmark' results David Mansfield
2003-01-24 23:03         ` Andrew Morton
2003-01-27 15:14           ` David Mansfield
2003-01-24 22:40     ` 2.5.59mm5, raid1 resync speed regression Mitchell Blank Jr

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=3E31701E.4020101@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dm.cobite.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox