linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Andrew Clayton <andrew@digital-domain.net>
Cc: John Stoffel <john@stoffel.org>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	David Rees <drees76@gmail.com>, Andrew Clayton <andrew@pccl.info>,
	linux-raid@vger.kernel.org
Subject: Re: RAID 5 performance issue.
Date: Fri, 5 Oct 2007 16:56:03 -0400	[thread overview]
Message-ID: <18182.42211.405326.261727@stoffel.org> (raw)
In-Reply-To: <20071005204207.2d338375@alpha.digital-domain.net>


Andrew> On Fri, 5 Oct 2007 15:02:22 -0400, John Stoffel wrote:
>> 
>> How much memory does this system have?  Have you checked the output of

Andrew> 2GB

>> /proc/mtrr at all?  There' have been reports of systems with a bad

Andrew> $ cat /proc/mtrr 
Andrew> reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1

That looks to be good, all the memory is there all in the same
region.  Oh well... it was a thought. 

>> BIOS that gets the memory map wrong, causing access to memory to slow
>> down drastically.

Andrew> BIOS-provided physical RAM map:
Andrew>  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Andrew>  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Andrew>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Andrew>  BIOS-e820: 0000000000100000 - 000000007fff0000 (usable)
Andrew>  BIOS-e820: 000000007fff0000 - 000000007ffff000 (ACPI data)
Andrew>  BIOS-e820: 000000007ffff000 - 0000000080000000 (ACPI NVS)
Andrew>  BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)

I dunno about this part.  

Andrew> full dmesg (from 2.6.21-rc8-git2) at
Andrew> http://digital-domain.net/kernel/sw-raid5-issue/dmesg

>> So if you have 2gb of RAM, try booting with mem=1900m or something

Andrew> Worth a shot.

It might make a difference, might not.  Do you have any kernel
debugging options turned on?  That might also be an issue.  Check your
.config, there are a couple of options which drastically slow down the
system. 

>> like that and seeing if things are better for you.
>> 
>> Make sure your BIOS is upto the latest level as well.

Andrew> Hmm, I'll see whats involved in that.
 
At this point, I don't suspect the BIOS any more.  

Can you start a 'vmstat 1' in one window, then start whatever you do
to get crappy performance.  That would be interesting to see.

John

  reply	other threads:[~2007-10-05 20:56 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03  9:53 RAID 5 performance issue Andrew Clayton
2007-10-03 16:43 ` Justin Piszcz
2007-10-03 16:48   ` Justin Piszcz
2007-10-03 20:10     ` Andrew Clayton
2007-10-03 20:16       ` Justin Piszcz
2007-10-06 12:30       ` Justin Piszcz
2007-10-06 16:05         ` Justin Piszcz
2007-10-03 20:19   ` Andrew Clayton
2007-10-03 20:35     ` Justin Piszcz
2007-10-03 20:46       ` Andrew Clayton
2007-10-03 20:36     ` David Rees
2007-10-03 20:48       ` Andrew Clayton
2007-10-04 14:08       ` Andrew Clayton
2007-10-04 14:09         ` Justin Piszcz
2007-10-04 14:10           ` Justin Piszcz
2007-10-04 14:44             ` Andrew Clayton
2007-10-04 16:20               ` Justin Piszcz
2007-10-04 18:26                 ` Andrew Clayton
2007-10-05 10:25                   ` Justin Piszcz
2007-10-05 10:57                     ` Andrew Clayton
2007-10-05 11:08                       ` Justin Piszcz
2007-10-05 12:53                         ` Andrew Clayton
2007-10-05 13:18                           ` Justin Piszcz
2007-10-05 13:30                           ` Andrew Clayton
2007-10-05 14:07                             ` Justin Piszcz
2007-10-05 14:32                               ` Andrew Clayton
2007-10-05 16:10                               ` Andrew Clayton
2007-10-05 16:16                                 ` Justin Piszcz
2007-10-05 19:33                                   ` Andrew Clayton
2007-10-05 18:58                                 ` Richard Scobie
2007-10-05 19:02                                   ` Justin Piszcz
2007-10-05 19:02               ` John Stoffel
2007-10-05 19:42                 ` Andrew Clayton
2007-10-05 20:56                   ` John Stoffel [this message]
2007-10-07 17:22                     ` Andrew Clayton
2007-10-11 17:06                       ` Bill Davidsen
2007-10-11 18:07                         ` Andrew Clayton
2007-10-11 23:43                           ` Justin Piszcz
2007-10-04 14:36           ` Andrew Clayton
2007-10-04 14:39             ` Justin Piszcz
2007-10-04 15:03               ` Andrew Clayton
2007-10-04 16:19                 ` Justin Piszcz
2007-10-04 19:01                   ` Andrew Clayton
2007-10-04 16:46                 ` Steve Cousins
2007-10-04 17:06                   ` Steve Cousins
2007-10-04 19:06                   ` Andrew Clayton
2007-10-05 10:20                     ` Justin Piszcz
2007-10-04 14:39             ` Justin Piszcz
2007-10-03 17:53 ` Goswin von Brederlow
2007-10-03 20:20   ` Andrew Clayton
2007-10-03 20:48     ` Richard Scobie
2007-10-05 20:25 ` Brendan Conoboy
2007-10-06  0:38   ` Dean S. Messing
2007-10-06  8:18     ` Justin Piszcz
2007-10-08  1:40       ` Dean S. Messing
2007-10-08  8:44         ` Justin Piszcz

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=18182.42211.405326.261727@stoffel.org \
    --to=john@stoffel.org \
    --cc=andrew@digital-domain.net \
    --cc=andrew@pccl.info \
    --cc=drees76@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).