From: Emmanuel Florac <eflorac@intellique.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: External log size limitations
Date: Sat, 19 Feb 2011 22:47:05 +0100 [thread overview]
Message-ID: <20110219224705.7fa0a66c@galadriel2.home> (raw)
In-Reply-To: <4D602936.10400@hardwarefreak.com>
Le Sat, 19 Feb 2011 14:33:58 -0600 vous écriviez:
> To bring this back around to the OP's original question, do you agree
> or disagree with my assertion that a 64 KiB XFS block size will yield
> little if any advantage over a 4 KiB block size, and may in fact have
> some disadvantages, specifically with small file random IO?
Undoubtly. The very big block size of Exastore probably is due to its
parallel cluster configuration; all parallel clusters filesystems I
know of (Lustre, PVFS2, CEPH, Isilon, etc) use 64K or bigger blocks.
The exastore big block size is a constraint due to its architecture,
not a desirable improvement. In fact, exanet suffered from many
performance problems, because general use parallel clusters are hard.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-19 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 18:54 External log size limitations Andrew Klaassen
2011-02-17 0:32 ` Dave Chinner
2011-02-18 15:26 ` Andrew Klaassen
2011-02-18 19:55 ` Stan Hoeppner
2011-02-18 20:31 ` Andrew Klaassen
2011-02-19 3:53 ` Stan Hoeppner
2011-02-19 10:02 ` Matthias Schniedermeyer
2011-02-19 20:33 ` Stan Hoeppner
2011-02-19 21:47 ` Emmanuel Florac [this message]
2011-02-20 21:14 ` Dave Chinner
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=20110219224705.7fa0a66c@galadriel2.home \
--to=eflorac@intellique.com \
--cc=stan@hardwarefreak.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