From: rwhron@earthlink.net
To: Andrea Arcangeli <andrea@suse.de>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org,
ltp-list@lists.sourceforge.net
Subject: Re: VM test on 2.4.13-pre3aa1 (compared to 2.4.12-aa1 and 2.4.13-pre2aa1)
Date: Wed, 17 Oct 2001 00:48:39 -0400 [thread overview]
Message-ID: <20011017004839.A15996@earthlink.net> (raw)
In-Reply-To: <20011016081639.A209@earthlink.net> <20011017021242.S2380@athlon.random> <20011017043103.D2380@athlon.random>
In-Reply-To: <20011017043103.D2380@athlon.random>; from andrea@suse.de on Wed, Oct 17, 2001 at 04:31:03AM +0200
On Wed, Oct 17, 2001 at 04:31:03AM +0200, Andrea Arcangeli wrote:
> I noticed that anotehr thing that changed between vanilla 2.4.13pre2 and
> 2.4.13pre3 is the setting of page_cluster on machine with lots of ram.
>
> You'll now find the page_cluster set to 6, that means "1 << 6 << 12"
> bytes will be paged in at each major fault, while previously only "1 <<
> 4 << 12" bytes were paged in.
>
> So I'd suggest to try again after "echo 4 > /proc/sys/vm/page-cluster"
> to see if it makes any difference.
>
> Andrea
You Rule!
The tweak to page-cluster is basically magic for this test.
With page-cluster=4, the mp3blaster sputtered like 2.4.13pre2aa1.
Better, but not beautiful.
Real beauty happens with page-cluster=2. There is virtually no sputter.
And the wall clock time is a little better than 2.4.13pre2aa1!
I don't know what page-cluster size is best for everything, but
2.4.12aa1 (which was very good IMHO), sputtered about 10 seconds per
iteration, and each iteration took 64 seconds.
2.4.13pre3aa1 with no sputters: 48 seconds.
Amazing!
Also, interactive "feel" is much better too. This test would
really brutalize keyboard response. With 2.4.13-pre3aa1 and
page-cluster=2, the box is still usable. (for more than listening
to mp3's :))
page-cluster = 6
Averages for 10 mtest01 runs
bytes allocated: 1236166246
User time (seconds): 2.299
System time (seconds): 2.951
Elapsed (wall clock) time: 41.969
Percent of CPU this job got: 12.00
Major (requiring I/O) page faults: 113.5
Minor (reclaiming a frame) faults: 302580.3
page-cluster = 4
Averages for 10 mtest01 runs
bytes allocated: 1237529395
User time (seconds): 2.097
System time (seconds): 2.788
Elapsed (wall clock) time: 49.394
Percent of CPU this job got: 9.50
Major (requiring I/O) page faults: 120.3
Minor (reclaiming a frame) faults: 302914.1
page-cluster = 2
Averages for 10 mtest01 runs
bytes allocated: 1239521689
User time (seconds): 2.051
System time (seconds): 2.785
Elapsed (wall clock) time: 47.878
Percent of CPU this job got: 9.80
Major (requiring I/O) page faults: 114.0
Minor (reclaiming a frame) faults: 303399.7
The wall clock time went up somewhat from page-cluster=6.
Here is where we were before:
2.4.13-pre2aa1
Averages for 10 mtest01 runs
bytes allocated: 1245184000
User time (seconds): 2.050
System time (seconds): 2.874
Elapsed (wall clock) time: 49.513
Percent of CPU this job got: 9.70
Major (requiring I/O) page faults: 115.6
Minor (reclaiming a frame) faults: 304781.9
2.4.12aa1
Averages for 10 mtest01 runs
bytes allocated: 1253362892
User time (seconds): 2.099
System time (seconds): 2.823
Elapsed (wall clock) time: 64.109
Percent of CPU this job got: 7.50
Major (requiring I/O) page faults: 135.2
Minor (reclaiming a frame) faults: 306779.8
--
Randy Hron
next prev parent reply other threads:[~2001-10-17 4:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 12:16 rwhron
2001-10-17 0:12 ` Andrea Arcangeli
2001-10-17 1:32 ` Beau Kuiper
2001-10-17 2:09 ` Andrea Arcangeli
2001-10-18 19:36 ` bill davidsen
2001-10-18 23:27 ` Andrea Arcangeli
2001-10-17 2:31 ` Andrea Arcangeli
2001-10-17 4:48 ` rwhron [this message]
2001-10-17 16:27 ` Linus Torvalds
2001-10-17 15:19 ` Marcelo Tosatti
2001-10-18 19:45 ` Bill Davidsen
2001-10-17 3:59 ` rwhron
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=20011017004839.A15996@earthlink.net \
--to=rwhron@earthlink.net \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.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
all inboxes | Powered by JetHome®