From: Eric Lowe <elowe@myrile.madriver.k12.oh.us>
To: linux-mm@kvack.org
Subject: page-cluster tuning
Date: Wed, 11 Oct 2000 07:34:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSF.4.10.10010110729380.38557-100000@myrile.madriver.k12.oh.us> (raw)
Hi,
Over the weekend I played with page-cluster after booting my
box with mem=8M. I ran a kernel build and updatedb simultaneously
driving it into the swap rather heavily during I/O and found that
_both_ processes made much more progress with page-cluster set
to 8 than to 4, and the default of 2 was painfully slow because
it didn't swap agressively enough.
I have yet to do any streaming I/O while swapping tests, but
should get to it later in the week. Would anybody like to
confirm my results that 8 appears to be an optimum value for
page-cluster in 8MB?
More to come..
--
Eric Lowe
Software Engineer, Systran Corporation
elowe@systran.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
reply other threads:[~2000-10-11 11:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.BSF.4.10.10010110729380.38557-100000@myrile.madriver.k12.oh.us \
--to=elowe@myrile.madriver.k12.oh.us \
--cc=linux-mm@kvack.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