From: Neil Brown <neilb@suse.de>
To: Federico <undicizeri@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1 extreme low performance
Date: Tue, 16 Dec 2008 13:35:23 +1100 [thread overview]
Message-ID: <18759.5099.172915.369111@notabene.brown> (raw)
In-Reply-To: message from Federico on Friday December 12
On Friday December 12, undicizeri@gmail.com wrote:
> I all,
> a couple of weeks ago I've updated the kernel (now I'm using .27-7)
> and mdadm to version 2.6.7 and now I have terrible RAID1 performance:
> during I/O operation I have 100% cpu utilization and all the system
> freeze until the operation ends. Seeking and reading from the RAID is
> extremely slow (sometime 4 or 5 seconds just to show an "ls -l"
> output) and writing is even worst.
> I've tested the same hard disk without RAID and It seem working well.
What filesystem are you using on the RAID?
If you disable barriers (maybe -o barriers=0 or -o nobarriers) does
that change the performance?
NeilBrown
prev parent reply other threads:[~2008-12-16 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 12:47 RAID1 extreme low performance Federico
2008-12-16 2:35 ` Neil Brown [this message]
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=18759.5099.172915.369111@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=undicizeri@gmail.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