From: Andrea Arcangeli <andrea@suse.de>
To: jogi@planetzork.ping.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13pre5aa1
Date: Mon, 22 Oct 2001 02:04:29 +0200 [thread overview]
Message-ID: <20011022020429.C8408@athlon.random> (raw)
In-Reply-To: <20011019061914.A1568@athlon.random> <20011021211726.A476@planetzork.spacenet>
In-Reply-To: <20011021211726.A476@planetzork.spacenet>; from jogi@planetzork.ping.de on Sun, Oct 21, 2001 at 09:17:26PM +0200
On Sun, Oct 21, 2001 at 09:17:26PM +0200, jogi@planetzork.ping.de wrote:
> 2.4.13-pre3aa1: 4:54.39 6:00.32 10:15.06 *
^^^^^^^^
> 2.4.13-pre5aa1: 4:54.61 5:10.38 5:19.68 5:40.37
^^^^^^^
this is interesting. I'm also wondering what you'd get if you used:
echo 8 > /proc/sys/vm/vm_scan_ratio
echo 1 > /proc/sys/vm/vm_mapped_ratio
echo 3 > /proc/sys/vm/vm_balance_ratio
(or also the other combination that I suggested in the other emails)
Anyways you can probably skip the above test and wait for a further
update that changes more than just the default sysctl values (also
notably it introduces the PG_launder logic originated from a discussion
with Marcelo and Linus, resemling somehow part of the PG_wait_for_IO
write throttling logic that I had in 2.4.12aa1 and 2.4.13pre3aa1, but I
doubt pre3aa1 was slower because of that, and in case next -aa will
slowdown again I'll later ask you to try with a one liner patch that
will disable the write throttling for writepage again [like pre5aa1 did]
just to make sure it's not the one that hurts :)
thanks to you too for the feedback!
Andrea
next prev parent reply other threads:[~2001-10-22 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 4:19 2.4.13pre5aa1 Andrea Arcangeli
2001-10-19 5:48 ` 2.4.13pre5aa1 Robert Love
2001-10-21 19:17 ` 2.4.13pre5aa1 jogi
2001-10-22 0:04 ` Andrea Arcangeli [this message]
[not found] ` <Pine.LNX.4.33L.0110211749310.3690-100000@imladris.surriel.com>
2001-10-22 11:08 ` 2.4.13pre5aa1 jogi
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 7:14 2.4.13pre5aa1 Dipankar Sarma
2001-10-20 14:10 2.4.13pre5aa1 Maneesh Soni
2001-10-22 10:01 ` 2.4.13pre5aa1 Andrea Arcangeli
2001-10-20 14:18 2.4.13pre5aa1 Maneesh Soni
2001-10-21 18:41 2.4.13pre5aa1 khromy
2001-10-21 23:51 ` 2.4.13pre5aa1 Andrea Arcangeli
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=20011022020429.C8408@athlon.random \
--to=andrea@suse.de \
--cc=jogi@planetzork.ping.de \
--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