From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: "Ken Brownfield" <brownfld@irridia.com>
Cc: "Rik van Riel" <riel@conectiva.com.br>,
"Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
linux-kernel@vger.kernel.org, "Andrea Arcangeli" <andrea@suse.de>
Subject: Re: [PATCH *] rmap VM 11c (RMAP IS A WINNER!)
Date: Sat, 19 Jan 2002 00:08:30 -0500 [thread overview]
Message-ID: <02f801c1a0a7$5643a1a0$02c8a8c0@kroptech.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201171721230.32617-100000@imladris.surriel.com> <012d01c19fb7$ba1cb680$02c8a8c0@kroptech.com> <20020118182837.D31076@asooo.flowerfire.com>
Ken Brownfield:
> Do you get more even throughput with this:
>
> /bin/echo "10 0 0 0 500 3000 10 0 0" > /proc/sys/vm/bdflush
>
> It seems to help significantly for me under heavy sustained I/O load.
With a little modification, Ken's suggestion makes -rmap11c a winner on my test
case.
/bin/echo "10 0 0 0 500 3000 30 0 0" > /proc/sys/vm/bdflush
Switching to synchronous bdflush a little later than Ken did brings performance
up to ~2000 blocks/sec, which is similar to older -ac kernels. This writeout
rate is very consistent (even more so than -ac) and seems to be the top end in
all large writes to the RAID (tried FTP, samba, and local balls-to-the-wall "cat
/dev/zero >..."), which helps show that this is not a network driver or protocol
interaction.
The same bdflush tuning (leaving aa's additional parameters at their defaults)
on 2.4.18pre2aa2 yields some improvement, but rmap is consistently faster by a
good margin. 2.4.17 performs worse with this tuning and is pretty much eating
dust at this point.
Latest Results:
2.4.17-rmap11c: 5:41 (down from 6:58)
2.4.18-pre2aa2: 6:31 (down from 7:10)
2.4.17: 7:06 (up from 6:57)
Congrats, Rik and thanks, Ken!
--Adam
next prev parent reply other threads:[~2002-01-19 5:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 19:22 [PATCH *] rmap VM 11c Rik van Riel
2002-01-17 23:59 ` Bill Davidsen
2002-01-18 0:05 ` Rik van Riel
2002-01-18 0:33 ` Adam Kropelin
2002-01-18 0:56 ` Rik van Riel
2002-01-18 10:06 ` Roy Sigurd Karlsbakk
[not found] ` <20020118182837.D31076@asooo.flowerfire.com>
2002-01-19 5:08 ` Adam Kropelin [this message]
2002-01-19 17:50 ` [PATCH *] rmap VM 11c (RMAP IS A WINNER!) Andrea Arcangeli
2002-01-19 18:39 ` Adam Kropelin
2002-01-19 20:21 ` Andrea Arcangeli
2002-01-19 22:15 ` Adam Kropelin
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='02f801c1a0a7$5643a1a0$02c8a8c0@kroptech.com' \
--to=akropel1@rochester.rr.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=andrea@suse.de \
--cc=brownfld@irridia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@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