public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: Dave Jones <davej@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18pre4aa1
Date: Fri, 25 Jan 2002 09:57:37 -0500	[thread overview]
Message-ID: <20020125095737.A1129@earthlink.net> (raw)
In-Reply-To: <20020124222357.C901@earthlink.net> <Pine.LNX.4.33L.0201250132450.32617-100000@imladris.surriel.com> <20020125132653.A28068@suse.de>
In-Reply-To: <20020125132653.A28068@suse.de>; from davej@suse.de on Fri, Jan 25, 2002 at 01:26:53PM +0100

>  it may be useful if Randy can throw a real world test
>  into the benchmarking, to get a better comparison of
>  the various systems. The obvious one that springs to mind
>  would be something like compilation of a large source tree

Thanks for the feedback.

2.5.2-dj5 wins the lucky "first-timer" award on the new tests.

Extract/configure/make/check autoconf-2.52:
Executes over 100000 processes and creates a lot of small
temporary files.  Won't hit the disk much on this box.

Extract/Configure/make/test perl-5.6.1:
For perl, "make test" is executed 5 times.  "make test" is about 
75% system and 25% user, which may provide more variation between 
kernel versions.

>  Or maybe timing an updatedb. Its realworld enough in that its
>  a daily task, generates lots of IO..

I'll time updatedb too.  updatedb may vary over time, depending
on how many src trees are extracted.  I'll make an effort to
keep that variable consistent.

-- 
Randy Hron


  reply	other threads:[~2002-01-25 14:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24  5:23 2.4.18pre4aa1 rwhron
2002-01-24  6:27 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-25  0:09   ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28  9:53     ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 15:29       ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28 20:28         ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 23:40           ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-29  0:15             ` 2.4.18pre4aa1 Daniel Phillips
2002-01-29 13:05               ` 2.4.18pre4aa1 Pavel Machek
2002-01-25  0:19   ` 2.4.18pre4aa1 rwhron
2002-01-25  0:29     ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  3:23       ` 2.4.18pre4aa1 rwhron
2002-01-25  3:35         ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  4:56           ` 2.4.18pre4aa1 rwhron
2002-01-25  4:57             ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  5:18               ` 2.4.18pre4aa1 David Weinehall
2002-01-25 17:03                 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 17:29                   ` 2.4.18pre4aa1 Dave Jones
2002-01-25 12:26           ` 2.4.18pre4aa1 Dave Jones
2002-01-25 14:57             ` rwhron [this message]
2002-01-28  0:37         ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-25  0:11 ` 2.4.18pre4aa1 Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22  6:48 2.4.18pre4aa1 Andrea Arcangeli
2002-01-22  6:58 ` 2.4.18pre4aa1 Robert Love
2002-01-22  7:37   ` 2.4.18pre4aa1 Dan Chen
2002-01-22  7:43     ` 2.4.18pre4aa1 Robert Love
2002-01-22 10:02     ` 2.4.18pre4aa1 Russell King
2002-01-22 10:12       ` 2.4.18pre4aa1 Robert Love

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=20020125095737.A1129@earthlink.net \
    --to=rwhron@earthlink.net \
    --cc=davej@suse.de \
    --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