From: Josh McKinney <forming@home.com>
To: linux-kernel@vger.kernel.org
Cc: forming@home.com
Subject: Re: Fwd: VM testing with mtest, 2.4.12-ac3, 2.4.12-ac3+riel's patches, and 2.4.13aa1
Date: Thu, 18 Oct 2001 12:26:18 -0500 [thread overview]
Message-ID: <20011018122618.A17682@cy599856-a.home.com> (raw)
In-Reply-To: <20011018015112.A3763@cy599856-a.home.com> <20011018090646.B1144@turbolinux.com>
In-Reply-To: <20011018090646.B1144@turbolinux.com>
On approximately Thu, Oct 18, 2001 at 09:06:46AM -0600, Andreas Dilger wrote:
> On Oct 18, 2001 01:51 -0500, Josh McKinney wrote:
> > This is a report of the mtest01 scripts posted by rwhron@earthlink.net
> > a day orso ago.
> >
> > The numbers are rather interesting. While the latency of the ac kernels is
> > definitely better, the song only dropped out for a second or two in the
> > begining but that was it. The aa kernel drops out more frequently throughout
> > the test, but the amount of memory allocated is almost twice as much as with
> > the ac kernels.
>
> -ac kernel:
> > Averages for 10 mtest01 runs
> > bytes allocated: 134427443.2
> > User time (seconds): 2.546
> > System time (seconds): 1.370
> > Elapsed (wall clock) time: 4.798
> > Percent of CPU this job got: 89.1%
> > Major (requiring I/O) page faults: 103.8
> > Minor (reclaiming a frame) faults: 32702
>
> -ac kernel + Rik's patches:
> > Averages for 10 mtest01 runs
> > bytes allocated: 124885401.6
> > User time (seconds): 2.380
> > System time (seconds): 1.253
> > Elapsed (wall clock) time: 4.401
> > Percent of CPU this job got: 89.1%
> > Major (requiring I/O) page faults: 100.2
> > Minor (reclaiming a frame) faults: 30363.3
>
> Linus kernel:
> > Averages for 10 mtest01 runs
> > bytes allocated: 288148684.8
> > User time (seconds): 5.496
> > System time (seconds): 3.003
> > Elapsed (wall clock) time: 12.250
> > Percent of CPU this job got: 68.9%
> > Major (requiring I/O) page faults: 103.5
> > Minor (reclaiming a frame) faults: 70380.6
>
> Note that the Linus kernel has allocated twice as much memory. What does that
> mean exactly? The user/system/wall time is also twice as high. Somehow I
> don't think you are having an equal test.
>
> Cheers, Andreas
I thought that was strange myself, which is why I metioned it in the begining.
Also when I seen the results I reran the tests, all in single user mode,
freshreboot, put linux single on the CL, voila, sh mtest01.sh & mpg123 some.mp3,
and there is my test. I know the numbers are crazy and I also know the
importance of having all other variables the same.
Josh
--
Linux, the choice | Animals can be driven crazy by putting too
of a GNU generation -o) | many in too small a pen. Homo sapiens is
Kernel 2.4.13-pre3 /\ | the only animal that voluntarily does this
on a i586 _\_v | to himself. -- Lazarus Long
|
prev parent reply other threads:[~2001-10-18 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 6:51 Josh McKinney
2001-10-18 15:06 ` Andreas Dilger
2001-10-18 17:26 ` Josh McKinney [this message]
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=20011018122618.A17682@cy599856-a.home.com \
--to=forming@home.com \
--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
all inboxes | Powered by JetHome®