public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Alex Tomas <bzzz@tmi.comex.ru>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>, anton@samba.org
Subject: Re: [PATCH] concurrent block allocation for ext3
Date: Fri, 14 Mar 2003 18:56:37 -0800	[thread overview]
Message-ID: <251250000.1047696997@flay> (raw)
In-Reply-To: <227420000.1047676948@flay>

> SDET on my machine (16x NUMA-Q) has fallen in love with your patch, 
> and has decided to elope with it to a small desert island. This is 
> despite it's one disk hung off node 0, and the IO througput of a 
> slightly damp piece of cotton thread. Apologies for the loss of your 
> patch as it gets whisked away ;-)

Dbench (1 disk, x440 8 real cpus, 16 HT ones)

before: 
Throughput 265.032 MB/sec (NB=331.29 MB/sec  2650.32 MBit/sec)  256 procs
after:
Throughput 381.964 MB/sec (NB=477.454 MB/sec  3819.64 MBit/sec)  256 procs

(I took the second run, first ones are slower, seems to be stable after)

NUMA-Q 16-way (1 disk. 16 cpus)

before:
Throughput 48.5304 MB/sec (NB=60.663 MB/sec  485.304 MBit/sec)  256 procs
after:
Throughput 58.8483 MB/sec (NB=73.5603 MB/sec  588.483 MBit/sec)  256 procs

NUMA-Q has slower disks, old adaptors, and a slow cross-node interconnect.


  reply	other threads:[~2003-03-15  2:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 15:41 [PATCH] concurrent block allocation for ext3 Alex Tomas
2003-03-10 16:25 ` Andreas Dilger
2003-03-10 16:33   ` Alex Tomas
2003-03-10 16:43   ` Daniel Phillips
2003-03-14 21:22 ` Martin J. Bligh
2003-03-15  2:56   ` Martin J. Bligh [this message]
2003-03-15  6:08     ` Martin J. Bligh

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=251250000.1047696997@flay \
    --to=mbligh@aracnet.com \
    --cc=akpm@digeo.com \
    --cc=anton@samba.org \
    --cc=bzzz@tmi.comex.ru \
    --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