public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Samium Gromoff <deepfire@sic-elvis.zel.ru>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [TEST] 2.4 vs 2.6.2 vs 2.6.2-mm1 vs 2.6.2-rc3-mm1
Date: Tue, 10 Feb 2004 16:33:37 +0300	[thread overview]
Message-ID: <871xp3hxe6.wl@canopus.ns.zel.ru> (raw)
In-Reply-To: <4028D450.4030504@cyberone.com.au>

At Tue, 10 Feb 2004 23:53:36 +1100,
Nick Piggin wrote:
> Samium Gromoff wrote:
[snip]
> >		2.4.20-pre9	2.6.2		2.6.2-mm1	2.6.2-rc3-mm1
> >
> >Load 1
> >  run1		6.27		9.14		9.42		10.52
> >
> >Load 2
> >  run1		3.29		4.42		3.40		3.45
> >  run2		3.28		4.37		3.39		3.45
> >
> >Load 3
> >  run1		4.42		8.39		18.26
> >
> >
> >short summary:
> >
> >	2.4 is faster.
> >
> >
> 
> What are the units? minutes.seconds?
Right.

> The test is interesting, I'll have to try it. Does it
> resemble a workload you're interested in?
Basically, yes.

> It looks like the -mm kernels might have something other
> than Nikita's and my VM patches that is affecting times.
> 
> Your Load 3 looks quite bad. Does it give decent results?
> Is it possibly because the other stuff is getting better
> treatment, do you think?
Everything else was basically idle.
The test script generated something like 15 rows of text,
which hardly could be considered noticeable...

> Thanks
> Nick

regards, Samium Gromoff



      reply	other threads:[~2004-02-10 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09 14:57 [TEST] 2.4 vs 2.6.2 vs 2.6.2-mm1 vs 2.6.2-rc3-mm1 Samium Gromoff
2004-02-09 15:46 ` Samium Gromoff
2004-02-10 12:53 ` Nick Piggin
2004-02-10 13:33   ` Samium Gromoff [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=871xp3hxe6.wl@canopus.ns.zel.ru \
    --to=deepfire@sic-elvis.zel.ru \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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