public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Steven Cole <scole@lanl.gov>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.1pre8 slowdown on dbench tests
Date: Wed, 24 Jan 2001 17:44:39 +0100	[thread overview]
Message-ID: <20010124174439.W16110@suse.de> (raw)
In-Reply-To: <01012208583400.01639@spc.esa.lanl.gov> <01012313294400.01045@spc.esa.lanl.gov> <20010123215419.A7435@suse.de> <01012409085700.02477@spc.esa.lanl.gov>
In-Reply-To: <01012409085700.02477@spc.esa.lanl.gov>; from scole@lanl.gov on Wed, Jan 24, 2001 at 09:08:57AM -0700

On Wed, Jan 24 2001, Steven Cole wrote:
> > Thanks! Could I talk you into doing one last run? pre8 with
> > include/linux/elevator.h having these values set for
> > ELEVATOR_LINUS:
> >
> Here are two sets of dbench 48 runs with that mod. I can't explain why the
> second set is faster.  The second set was performed with no reboot after the 
> first set.  The individual runs were performed with no wait in-between.

Was this the 2.4.1-pre8x tree? Regardless, it's about back to the
same dbench performance that we saw earlier with the more unfair
setup. The blk-xx changes in recent 2.4.1-pre were not meant (and
never claimed :-) to boost dbench performance. That's actually
quite easy to do: let one thread completely finish I/O, _then_
move on to the next one. This isn't what we want in Real Life.

The fact that dbench performance remains pretty good from stock
kernel against the changes I told you to do is excellent and
mainly due to the batch freeing changes.

In most real life situations, throughput on account of no care for
latency is not ideal. Even though dbench performance drops a bit,
you will see better distribution of the bandwidth between the
threads. Think file serving.

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-24 16:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01012208583400.01639@spc.esa.lanl.gov>
2001-01-22 20:30 ` 2.4.1pre8 slowdown on dbench tests Marcelo Tosatti
2001-01-22 23:11   ` Jens Axboe
2001-01-23 20:29     ` Steven Cole
2001-01-23 20:54       ` Jens Axboe
2001-01-24 16:08         ` Steven Cole
2001-01-24 16:44           ` Jens Axboe [this message]
2001-01-24 17:03             ` Steven Cole
2001-01-18 22:52 Steven Cole
2001-01-18 21:49 ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2001-01-18 17:17 Marcelo Tosatti
2001-01-18 20:18 ` Szabolcs Szakacsits
2001-01-19  2:23   ` Szabolcs Szakacsits
2001-01-19  2:13     ` Jens Axboe
2001-01-19  5:49       ` Szabolcs Szakacsits
2001-01-19  0:16 ` Andrea Arcangeli
2001-01-18 23:51   ` Marcelo Tosatti
2001-01-19  1:43     ` Jens Axboe
2001-01-19  1:40   ` Jens Axboe
2001-01-19  1:46     ` Andi Kleen
2001-01-19  1:47       ` Jens Axboe
2001-01-19  2:08         ` Andi Kleen
2001-01-19  2:10           ` Jens Axboe

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=20010124174439.W16110@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=scole@lanl.gov \
    /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