From: ebiederm@xmission.com (Eric W. Biederman)
To: "Gross, Mark" <mark.gross@intel.com>
Cc: "'Christopher E. Brown'" <cbrown@woods.net>,
"Griffiths, Richard A" <richard.a.griffiths@intel.com>,
"'Andrew Morton'" <akpm@zip.com.au>,
mgross@unix-os.sc.intel.com, "'Jens Axboe'" <axboe@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] RE: ext3 performance bottleneck as the number of s pindles gets large
Date: 24 Jun 2002 11:14:08 -0600 [thread overview]
Message-ID: <m1y9d4r44f.fsf@frodo.biederman.org> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C057B49C9@orsmsx111.jf.intel.com>
"Gross, Mark" <mark.gross@intel.com> writes:
> We are running the tests with the following mother board.
> http://www.intel.com/design/servers/scb2/index.htm?iid=ipp_browse+motherbd_s
> cb2&
>
> Its a very nice box with 2 independent 64/66 PCI buses.
> Capable of 2x503MB/sec, using your logic ;)
>
> Regardless, the 640MB/s number was computed without considering the PCI bus
> limitations, or the dual port nature of the base 160MB/sec nature of the
> Adabptec SCSI-39160.
> http://www.adaptec.com/worldwide/product/proddetail.html?sess=no&prodkey=ASC
> -39160&cat=Products
>
> Realistically, we are looking for a max throughput of about 320MB/sec with 4
> adapters with enough drives attached.
Careful even with at 320MB/sec this requires 50% of your systems theoretical
memory bandwidth in DMA transfers.
Application level benchmarks like streams can only achieve memory copy numbers
on a PIII platform of about 320MB/sec. A highly tuned mmx, or sse memory
copy can do better but it is a challenge.
That close to the hardware limits finding the actual bottleneck can
get very tricky. At the very least I would run the system with
just one processor, and attempt to get the numbers that way. I can
trivially see spinlock hold times staying high simply because
the memory is busy with a DMA transfer, and so cannot be used to
transfer the new contents of the lock.
Eric
next prev parent reply other threads:[~2002-06-24 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 16:33 Gross, Mark
2002-06-24 17:14 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 16:24 [Lse-tech] " Gross, Mark
2002-06-20 15:24 Griffiths, Richard A
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=m1y9d4r44f.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=cbrown@woods.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mark.gross@intel.com \
--cc=mgross@unix-os.sc.intel.com \
--cc=richard.a.griffiths@intel.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®