public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Con Kolivas <conman@kolivas.net>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] ext3, reiser, jfs, xfs effect on contest
Date: Fri, 31 Jan 2003 19:40:22 +0300	[thread overview]
Message-ID: <3E3AA6F6.3090504@namesys.com> (raw)
In-Reply-To: <20030131152156.GA15977@codemonkey.org.uk>

Dave Jones wrote:

>On Fri, Jan 31, 2003 at 04:56:07PM +0300, Hans Reiser wrote:
> > Try running with the -E option for gcc, it might be less CPU intensive, 
> > and thus a better FS benchmark.
> > 
> > What do you think?
>
>It's hardly a realistic real-world benchmark if you start nobbling
>bits of it though.  Not reading the preprocessed output is sure
>to bump the benchmark points on an fs optimised for lots of small
>writes.
>
>		Dave
>
>  
>
Sigh.  The alternative is to strace the compile, write a perl scipt or 
something to get just the FS related calls out of it, and then create a 
program with just the FS related calls.  gcc -E sounds easier to me.;-)

-- 
Hans



  reply	other threads:[~2003-01-31 16:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 13:20 [BENCHMARK] ext3, reiser, jfs, xfs effect on contest Con Kolivas
2003-01-31 13:37 ` Hans Reiser
2003-01-31 13:40   ` Con Kolivas
2003-01-31 13:56     ` Hans Reiser
2003-01-31 14:15       ` Con Kolivas
2003-01-31 15:21       ` Dave Jones
2003-01-31 16:40         ` Hans Reiser [this message]
2003-01-31 16:47           ` Dave Jones
2003-01-31 17:11             ` Hans Reiser
2003-01-31 19:04   ` Andrew Morton
2003-01-31 19:29     ` Hans Reiser
2003-01-31 22:21       ` Con Kolivas
2003-01-31 23:18         ` Con Kolivas
2003-02-01  0:19         ` David Lang
2003-01-31 14:09 ` Mike A. Harris
2003-01-31 14:18   ` Con Kolivas
2003-01-31 15:00   ` Maciej Soltysiak
2003-02-01  0:12 ` Con Kolivas

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=3E3AA6F6.3090504@namesys.com \
    --to=reiser@namesys.com \
    --cc=conman@kolivas.net \
    --cc=davej@codemonkey.org.uk \
    --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