From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Angelo McComis <angelo@mccomis.com>
Subject: Re: XFS use within multi-threaded apps
Date: Sun, 24 Oct 2010 20:22:46 +0200 [thread overview]
Message-ID: <201010242022.46693@zmi.at> (raw)
In-Reply-To: <AANLkTi=RZ=qf5xqMQNZjZaikAdw12PzbzD3vo-hZfNHT@mail.gmail.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 1724 bytes --]
On Samstag, 23. Oktober 2010 Angelo McComis wrote:
> They quoted having 10+TB databases running OLTP on EXT3 with
> 4-5GB/sec sustained throughput (not XFS).
Which servers and storage are these? This is nothing you can do with
"normal" storages. Using 8Gb/s Fibre Channel gives 1GB/s, if you can do
full speed I/O. So you'd need at least 5 parallel Fibre Channel storages
running without any overhead. Also, a single server can't do that high
rates, so there must be several front-end servers. That again means
their database must be especially organised for that type of load
(shared nothing or so).
On the other hand, if they have these performance numbers on 100 shared
serves, it only needs 51MB/s per server of I/O to get 5GB/s total
throughput. So that is a number without a lot of meaning, as long as you
don't know which hardware is used.
And: how high would be their throughput when using XFS instead EXT3? ;-)
One question comes to my mind: if they do direct I/O, would there still
be a lot of difference between XFS and EXT3, performance wise?
And how many companies run around telling which filesystem they use for
their performance critical business application? Normally they do this
only for marketing, so they get paid or special prices if they say "with
this product we are sooo happy".
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-24 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 13:42 XFS use within multi-threaded apps Angelo McComis
2010-10-19 1:12 ` Dave Chinner
2010-10-19 4:24 ` Stewart Smith
2010-10-20 12:00 ` Angelo McComis
2010-10-23 19:56 ` Peter Grandi
2010-10-23 20:59 ` Angelo McComis
2010-10-23 21:01 ` Angelo McComis
2010-10-24 2:13 ` Stan Hoeppner
2010-10-24 18:22 ` Michael Monnerie [this message]
2010-10-24 23:08 ` Dave Chinner
2010-10-25 3:12 ` Stan Hoeppner
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=201010242022.46693@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=angelo@mccomis.com \
--cc=xfs@oss.sgi.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