From: Andrew Clayton <andrew@digital-domain.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: David Rees <drees76@gmail.com>, Andrew Clayton <andrew@pccl.info>,
linux-raid@vger.kernel.org
Subject: Re: RAID 5 performance issue.
Date: Thu, 4 Oct 2007 15:44:41 +0100 [thread overview]
Message-ID: <20071004154441.31addcfe@zeus.pccl.info> (raw)
In-Reply-To: <Pine.LNX.4.64.0710041009530.8275@p34.internal.lan>
On Thu, 4 Oct 2007 10:10:02 -0400 (EDT), Justin Piszcz wrote:
> Also, did performance just go to crap one day or was it gradual?
IIRC I just noticed one day that firefox and vim was stalling. That was
back in February/March I think. At the time the server was running a
2.6.18 kernel, since then I've tried a few kernels in between that and
currently 2.6.23-rc9
Something seems to be periodically causing a lot of activity that
max's out the stripe_cache for a few seconds (when I was trying
to look with blktrace, it seemed pdflush was doing a lot of activity
during this time).
What I had noticed just recently was when I was the only one doing IO
on the server (no NFS running and I was logged in at the console) even
just patching the kernel was crawling to a halt.
> Justin.
Cheers,
Andrew
next prev parent reply other threads:[~2007-10-04 14:44 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 [this message]
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
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=20071004154441.31addcfe@zeus.pccl.info \
--to=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).