From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.38-mm2 dbench $N times
Date: Tue, 24 Sep 2002 17:31:39 -0700 [thread overview]
Message-ID: <3D9103EB.FC13A744@digeo.com> (raw)
In-Reply-To: 20020925001826.GM6070@holomorphy.com
William Lee Irwin III wrote:
>
> William Lee Irwin III wrote:
> >> Taken on 32x/32G NUMA-Q:
> >> Throughput 67.3949 MB/sec (NB=84.2436 MB/sec 673.949 MBit/sec) 16 procs
> >> dbench 16 11.72s user 122.21s system 422% cpu 31.733 total
>
> On Tue, Sep 24, 2002 at 10:47:30AM -0700, Andrew Morton wrote:
> > Taken on 2x/0.8G el-scruffo PC:
> > Throughput 135.02 MB/sec (NB=168.775 MB/sec 1350.2 MBit/sec)
> > ./dbench 16 12.11s user 16.29s system 181% cpu 15.646 total
> > What's up with that?
>
> Not sure. This is boot bay SCSI crud, but single-disk FC looks
> *worse* for no obvious reason. Multiple disk tests do much better
> (about matching the el-scruffo PC numbers above).
>
dbench 16 on that sort of machine is a memory bandwidth test.
And a dcache lock exerciser. It basically doesn't touch the
disk. Something very bad is happening.
Anton can get 3000 MByte/sec ;)
next prev parent reply other threads:[~2002-09-25 0:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 13:20 2.5.38-mm2 dbench $N times William Lee Irwin III
2002-09-24 17:47 ` Andrew Morton
2002-09-25 0:18 ` William Lee Irwin III
2002-09-25 0:25 ` William Lee Irwin III
2002-09-25 0:31 ` Andrew Morton [this message]
2002-09-25 0:39 ` William Lee Irwin III
2002-09-25 0:46 ` Andrew Morton
2002-09-25 1:08 ` Dave Hansen
2002-09-25 1:17 ` William Lee Irwin III
2002-09-25 6:03 ` Martin J. Bligh
2002-09-25 18:51 ` Andrew Theurer
2002-09-25 20:57 ` Martin J. Bligh
2002-09-25 21:05 ` Andrew Theurer
2002-09-25 23:57 ` William Lee Irwin III
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=3D9103EB.FC13A744@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.