From: Jens Axboe <axboe@suse.de>
To: Roger Larsson <roger.larsson@norran.net>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: Errors in the VM - detailed
Date: Fri, 1 Feb 2002 19:57:43 +0100 [thread overview]
Message-ID: <20020201195743.J12156@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0202011708460.29576-100000@mustard.heime.net> <200202011847.g11Ilwa14845@maila.telia.com>
In-Reply-To: <200202011847.g11Ilwa14845@maila.telia.com>
On Fri, Feb 01 2002, Roger Larsson wrote:
> On Fridayen den 1 February 2002 17.11, Roy Sigurd Karlsbakk wrote:
> > It does not seem to be possible to reproduce the error with apache2. But
> > this may be because Apache2's i/o handling doesn't impress much. With Tux,
> > I keep getting up to 40 megs per sec, but with Apache the average is
> > ~15MB/s.
> >
> > Btw ... It looks like your patch (against rmap12a) gave me an extra
> > performance kick. 12c gave me a max of ~32MB/s, whereas your patch
> > highered this to ~41.
> >
>
> Hmm.. suppose this is the problem anyway and that Jens patch was not enough.
> How do the disk drive sound during the test?
>
> Does it start to sound more when performance goes down?
Yes that would be interesting to know, if the disk becomes seek bound.
> About Jens patch:
>
> My feeling is that there should be (a lot) more READA than READ.
> since sequential READ really only NEEDS one at a time.
Probably, my patch was really just a quick try to see if it changed
anything.
> Number of READ limits the number of concurrent streams.
> And READA limits the maximum total read ahead.
Correct, Roy you could try and change the READA balance by allocating
lots more READA requests. Simply play around with the
queue_nr_requests / 4 setting. Try something "absurd" like
queue_nr_requests << 2 or even bigger.
--
Jens Axboe
next prev parent reply other threads:[~2002-02-01 18:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 15:05 Errors in the VM - detailed Roy Sigurd Karlsbakk
2002-01-31 15:44 ` David Mansfield
2002-01-31 20:21 ` Roger Larsson
2002-01-31 20:29 ` Jens Axboe
2002-01-31 20:43 ` Andrew Morton
2002-01-31 21:37 ` Jens Axboe
2002-02-01 16:05 ` Roy Sigurd Karlsbakk
2002-02-01 16:11 ` Roy Sigurd Karlsbakk
2002-02-01 18:44 ` Roger Larsson
2002-02-01 18:52 ` Roger Larsson
2002-02-01 18:57 ` Jens Axboe [this message]
2002-02-02 14:52 ` Roy Sigurd Karlsbakk
2002-02-02 14:43 ` Roy Sigurd Karlsbakk
2002-02-02 14:43 ` Roy Sigurd Karlsbakk
2002-02-02 14:44 ` Jens Axboe
2002-02-02 15:03 ` Roy Sigurd Karlsbakk
2002-02-02 15:06 ` Jens Axboe
2002-02-02 15:22 ` Errors in the VM - detailed (or is it Tux?) Roy Sigurd Karlsbakk
2002-02-02 15:31 ` Errors in the VM - detailed (or is it Tux? or rmap? or those together...) Roger Larsson
2002-02-02 15:38 ` Roy Sigurd Karlsbakk
2002-02-02 16:24 ` Roger Larsson
2002-02-02 16:39 ` Roy Sigurd Karlsbakk
2002-02-02 16:52 ` Roy Sigurd Karlsbakk
2002-02-02 17:29 ` Roger Larsson
2002-02-02 17:45 ` Errors in the VM - detailed Roy Sigurd Karlsbakk
2002-02-01 17:39 ` Denis Vlasenko
[not found] <OF675D993F.933C6CB9-ON88256B52.00595CCC@boulder.ibm.com>
2002-02-01 11:52 ` Roy Sigurd Karlsbakk
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=20020201195743.J12156@suse.de \
--to=axboe@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@norran.net \
--cc=roy@karlsbakk.net \
/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