mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17-rc1
Date: Fri, 14 Dec 2001 02:35:47 +0100	[thread overview]
Message-ID: <200112140138.fBE1c4529186@mailb.telia.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112131841080.28446-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0112131841080.28446-100000@freak.distro.conectiva>

On Thursday den 13 December 2001 21.44, Marcelo Tosatti wrote:
> Hi,
>
> I've just copied 2.4.17-rc1 to ftp.kernel.org... Its mirroring yet,
> probably.
>
> Well, I want people with the "unfreeable" buffer/cache problem to confirm
> with me that 2.4.17-rc1 is working ok.
>
> The same change which should fix that problem also should make 2.4 a bit
> less "swap happy".
>
>

Hi,

I have run some "files bigger than memory" (streaming) tests.
Some significant differences with earlier kernel:

* write - lowered throughput (26 MB/s => 22 MB/s)

* copy - throughput better by 2/3 (16 MB/s => 25 MB/s) !

* dbench 32 - back down to lower than 2.4.12 (due to increased fairness?)
	2.4.11				18.9 MB/s
	2.4.12				23.3 MB/s
	2.4.16				34.9 MB/s
	2.4.17-rc1			20.3 MB/s
	2.4.17-rc1 (file-readahead:1000)	24.5 MB/s
	[lets forget about them now...]

* diff - usage of "file-readahead" more than doubles efficency
	(most-kernels: 11 MB/s => 2.4.17-rc1 with readahead: 25 MB/s)

The nicest thing is that it is the first kernel where readahead tuning is not 
necessary for the copy operation.
Now it is only multiple-big-concurrent-reads that _needs_ "file-readahead"

/RogerL

-- 
Roger Larsson
Skellefteå
Sweden

  parent reply	other threads:[~2001-12-14  1:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 20:44 Marcelo Tosatti
2001-12-13 23:33 ` Ken Brownfield
2001-12-14  1:35 ` Roger Larsson [this message]
     [not found] ` <20011214061842.948118A6BA@cx518206-b.irvn1.occa.home.com>
2001-12-14 11:53   ` [BUG] 2.4.17-rc1 still has I/O freezing bug Ken Brownfield
2001-12-16  4:59 ` Linux 2.4.17-rc1 Daniel Phillips
2001-12-17 16:51   ` Marcelo Tosatti
2001-12-17 18:17   ` Richard Gooch
2001-12-17 21:00     ` Marcelo Tosatti
2001-12-16 14:13 ` David Relson
2001-12-16 14:19   ` Rik van Riel
2001-12-16 14:26   ` Dave Jones
2001-12-16 15:32     ` Ed Tomlinson
2001-12-16 15:37   ` David Relson
2001-12-16 16:10     ` John Alvord
2001-12-16 16:22     ` David Relson
2001-12-16 16:40       ` David Weinehall
2001-12-16 20:28   ` J Sloan
2001-12-18  1:27 ` Erik Andersen
2001-12-18  1:38   ` Dave Jones
2001-12-18  1:46     ` Erik Andersen
2001-12-18  1:53       ` Dave Jones
2001-12-14  1:18 Dieter Nützel
2001-12-16 19:25 Mario Vanoni
2001-12-17 11:30 Martin Knoblauch

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=200112140138.fBE1c4529186@mailb.telia.com \
    --to=roger.larsson@skelleftea.mail.telia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®