mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some dbench 32 results for 2.4.8-pre8, 2.4.7-ac10, and 2.4.7
Date: Fri, 10 Aug 2001 07:26:47 -0600	[thread overview]
Message-ID: <200108101328.f7ADSue26118@thor.mesatop.com> (raw)
In-Reply-To: <200108100502.f7A52Ve23324@thor.mesatop.com>
In-Reply-To: <200108100502.f7A52Ve23324@thor.mesatop.com>

Linus Torvalds wrote:
>Does the numbers change if you do something like
>
>	killall -STOP kupdated
>	echo 80 64 64 256 500 6000 90 > /proc/sys/vm/bdflush
>
>to make it less eager to write stuff out? (That just stops the
>every-five-second flush, and makes the dirty balancing numbers be 80/90%
>instead of the default 30/60%)
>
>In particular, the dirty balancing worked really badly before, and was
>just fixed.  I suspect that the bdflush numbers were tuned with the
>badly-working case, and they might be a bit too aggressive for dbench
>these days.. 

Sorry Linus for the late reply, but I went to bed just before your message.
I re-ran dbench 32 with the settings above.  Here are the results:
(Same conditions as in the previous tests otherwise).  Now, off to my day job.
 
Run #1 Throughput 12.7943 MB/sec    2.4.8-pre8
Run #2 Throughput 12.667 MB/sec     2.4.8-pre8
Run #3 Throughput 12.7091 MB/sec    2.4.8-pre8
 
Run #4 Throughput 13.7765 MB/sec    2.4.7
Run #5 Throughput 13.9632 MB/sec    2.4.7
Run #6 Throughput 13.9318 MB/sec    2.4.7

Steven


  parent reply	other threads:[~2001-08-10 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10  5:00 Steven Cole
2001-08-10  6:13 ` Linus Torvalds
2001-08-10 13:26 ` Steven Cole [this message]
2001-08-10 16:45   ` Linus Torvalds
2001-08-10 22:51     ` Steven Cole
2001-08-10 22:59       ` Steven Cole

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=200108101328.f7ADSue26118@thor.mesatop.com \
    --to=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®