All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Rivoir <s.rivoir@gts.it>
To: Voluspa <lista1@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disk performance degradation
Date: Wed, 30 Jul 2003 10:50:49 +0200	[thread overview]
Message-ID: <3F2786E9.9010808@gts.it> (raw)
In-Reply-To: <20030729182138.76ff2d96.lista1@telia.com>

Voluspa wrote:

> On 2003-07-29 12:00:06 Stefano Rivoir wrote:
> 
> 
>>Is there something I'm missing?!
> 
> 
> No, you are not ;-) You can reclaim some speed by doing a "hdparm -a
> 512". See thread for explanation (it's the borked value for readahead):

Thanks for the hint. This seems to make things a little better, but I'm
still far away from 2.4 performances. I thought that anticipatory sched
could be part of the problem, and booting with elevator=deadline
does a little better... but using 2.4 is completely another thing.
By the way, -a 512 vs -a 8 is a kernel "change" or an hdpam one?

Bye

-- 
Stefano RIVOIR
GTS Srl




  parent reply	other threads:[~2003-07-30  8:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 16:21 Disk performance degradation Voluspa
2003-07-29 16:50 ` Lou Langholtz
2003-07-30  4:17   ` Voicu Liviu
2003-07-30 21:02   ` Mike Dresser
2003-07-31  8:35     ` Måns Rullgård
2003-07-31 14:00       ` Mike Dresser
2003-07-31 21:15       ` Andrew Morton
2003-07-31 22:17         ` Bartlomiej Zolnierkiewicz
2003-07-30  8:50 ` Stefano Rivoir [this message]
2003-07-30 10:55   ` Andrew Morton
2003-07-30 16:06     ` Stefano Rivoir
2003-07-30 18:44       ` Andrew Morton
2003-07-31  0:21         ` Rahul Karnik
2003-07-31  6:59         ` Stefano Rivoir
2003-07-31  7:16           ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2003-07-30 11:43 Frederick, Fabian
2003-07-29 12:00 Stefano Rivoir

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=3F2786E9.9010808@gts.it \
    --to=s.rivoir@gts.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lista1@telia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.