From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: VM test on 2.4.14-pre3aa1 (compared to 2.4.14-pre3)
Date: Sun, 28 Oct 2001 08:13:32 -0500 [thread overview]
Message-ID: <20011028081332.A302@earthlink.net> (raw)
Summary: 2.4.14-pre3aa1 takes more wall time for
tests. Audio sounds closer to the "edge",
I.E more likely to skitter or skip.
Test: Run "mtest01 -w 80" and mmap001 from LTP.
Listen to long mp3 sampled at 128k.
Light console irc client and lynx use.
2.4.14-pre3aa1
About 2-3 seconds of sound skitter when typing
a URL in lynx or something in irc client.
Averages for 10 mtest01 runs
bytes allocated: 1246232576
User time (seconds): 2.105
System time (seconds): 2.773
Elapsed (wall clock) time: 59.503
Percent of CPU this job got: 7.80
Major (requiring I/O) page faults: 132.8
Minor (reclaiming a frame) faults: 305043.1
About 2-3 seconds of sound drop on mmap001 for
2.4.14-pre3aa1.
Average for 5 mmap001 runs
bytes allocated: 2048000000
User time (seconds): 19.660
System time (seconds): 16.272
Elapsed (wall clock seconds) time: 287.13
Percent of CPU this job got: 12.00
Major (requiring I/O) page faults: 500168.0
Minor (reclaiming a frame) faults: 38.8
2.4.14-pre3
Same two tests on 2.4.14-pre3 for comparison:
Averages for 10 mtest01 runs
bytes allocated: 1233859379
User time (seconds): 2.034
System time (seconds): 3.036
Elapsed (wall clock) time: 30.517
Percent of CPU this job got: 16.10
Major (requiring I/O) page faults: 107.0
Minor (reclaiming a frame) faults: 302029.3
Average for 5 mmap001 runs
bytes allocated: 2048000000
User time (seconds): 19.578
System time (seconds): 17.388
Elapsed (wall clock seconds) time: 171.45
Percent of CPU this job got: 21.20
Major (requiring I/O) page faults: 500158.8
Minor (reclaiming a frame) faults: 41.4
--
Randy Hron
reply other threads:[~2001-10-28 13:11 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=20011028081332.A302@earthlink.net \
--to=rwhron@earthlink.net \
--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