linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Carlo Wood <carlo@alinoe.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org
Subject: Re: SATA Harddisk speed drop of 100 MB/s
Date: Fri, 22 Jun 2007 22:31:32 -0300	[thread overview]
Message-ID: <20070623013132.GA1702@khazad-dum.debian.net> (raw)
In-Reply-To: <20070622212758.GA6970@alinoe.com>

Hi Carlo!

On Fri, 22 Jun 2007, Carlo Wood wrote:

> On Fri, Jun 22, 2007 at 06:17:46PM -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 22 Jun 2007, Carlo Wood wrote:
> > > So far I found out that it's RAID only.
> > 
> > If you change the IO schedulers, does it help?
> 
> How do I do that?

for i in /sys/block/sd*/queue/scheduler ; do echo -n "scheduler for $i was:" ; cat $i ; echo anticipatory > $i ; done

Should show you the scheduler for all libata/scsi discs, and switch to
anticipatory.  It probably works for hd* as well, but I don't have any
around to test.

I had ridiculous md raid performance (on resync) using cfq at least once.
Unfortunately I never bothered trying to track it down, and I didn't check
the throughput after the resync was done either. Also, I don't recall the
kernel version, but it was either 2.6.18 or 2.6.20.

Since it is a very simple test...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2007-06-23  1:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 22:48 SATA Harddisk speed drop of 100 MB/s Carlo Wood
2007-06-20 23:06 ` Jeff Garzik
2007-06-21  3:36   ` Arjan van de Ven
2007-06-22 16:21     ` Carlo Wood
2007-06-22 21:17       ` Henrique de Moraes Holschuh
2007-06-22 21:27         ` Carlo Wood
2007-06-23  1:31           ` Henrique de Moraes Holschuh [this message]
2007-06-23  2:59             ` Carlo Wood
2007-06-23 17:29               ` Andrew Morton
2007-06-23 22:21                 ` Jeff Garzik
2007-06-25 15:18               ` Lennart Sorensen
2007-06-25 16:04                 ` Carlo Wood
2007-06-22 21:44   ` SATA RAID5 " Carlo Wood
2007-06-23  3:54     ` Carlo Wood
2007-06-23  6:22       ` Tejun Heo
2007-06-22 21:48   ` Carlo Wood
2007-06-23  7:03     ` Jeff Garzik
2007-06-23  7:54       ` Tejun Heo
2007-06-23 12:53       ` Carlo Wood
2007-06-23 17:30         ` Bartlomiej Zolnierkiewicz
2007-06-23 22:43         ` Jeff Garzik
2007-06-24 11:58           ` Michael Tokarev
2007-06-24 12:59             ` Dr. David Alan Gilbert
2007-06-24 14:21               ` Justin Piszcz
2007-06-24 15:52                 ` Michael Tokarev
2007-06-24 16:59                   ` Justin Piszcz
2007-06-24 22:07                     ` Carlo Wood
2007-06-24 23:46                       ` Mark Lord
2007-06-25  0:23                       ` Patrick Mau
2007-06-24 15:48               ` Michael Tokarev
2007-07-05 22:12             ` Phillip Susi
2007-06-23  5:26 SATA Harddisk " Al Boldi

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=20070623013132.GA1702@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=arjan@infradead.org \
    --cc=carlo@alinoe.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@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).