public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18pre4aa1
Date: Fri, 25 Jan 2002 13:26:53 +0100	[thread overview]
Message-ID: <20020125132653.A28068@suse.de> (raw)
In-Reply-To: <20020124222357.C901@earthlink.net> <Pine.LNX.4.33L.0201250132450.32617-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0201250132450.32617-100000@imladris.surriel.com>; from riel@conectiva.com.br on Fri, Jan 25, 2002 at 01:35:08AM -0200

On Fri, Jan 25, 2002 at 01:35:08AM -0200, Rik van Riel wrote:

 > Considering the possible bad consequences for real
 > workloads, I'm not sure I want to make the system more
 > unfair just to better accomodate dbench ;)

 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
 kernel/mozilla/etc..  (same version, same config options
 every time). Though, as compilation is largely compute bound,
 instead of IO bound, the more small files that need to be
 read/generated the better.

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

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  parent reply	other threads:[~2002-01-25 12:30 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           ` Dave Jones [this message]
2002-01-25 14:57             ` 2.4.18pre4aa1 rwhron
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=20020125132653.A28068@suse.de \
    --to=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=rwhron@earthlink.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