public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS journaling position
Date: Wed, 27 Oct 2010 00:27:26 +0200	[thread overview]
Message-ID: <201010270027.26687@zmi.at> (raw)
In-Reply-To: <20101025161052.GC19425@sgi.com>


[-- Attachment #1.1: Type: Text/Plain, Size: 2081 bytes --]

On Montag, 25. Oktober 2010 Geoffrey Wehrman wrote:
> I haven't found any documentation to support this, but I have been
> told that the middle was selected for the single disk case to
> minimize seek times.  The distance the head must travel to or from
> other locations on the disk is optimized by placing the log in the
> middle of the disk.

This is based on the assumption that
1) a disk is totally filled with data and
2) the partition that XFS resides on is the only one on the disk.

For PCs or small servers you normally have a swap partition, the 
recommended size is RAMx2 (at least it was once suggested, I've always 
only set it to RAM size). Then you have at least a root filesystem, 
which often won't be XFS, and then the data partition, which could be a 
single partition until the end of the disk. For a single 300GB disk, 
this means that around 20-50GB will be used by "other" (swap, root, 
windows?) partitions, then maybe a single 250-280GB partition for XFS. 
If you place the journal in the middle of the partition, you are already 
in an area where disks are slower than on the outside. And if you fill 
only half of the partition, it means your log is totally on the end of 
the disk, access-wise.

So for the average single-disk setup, wouldn't a log at 25%-35% of the 
partition size be quicker than in the middle of the partition? Dave 
Chinner just recently said that "a partition which is 85% filled is 
full, from a filesystem view". That would already mean the log at 42% of 
the partition size would be better. (Greetings to Douglas Adams, again 
he was right ;-)

Just my 2¢, but I don't have a single disk machine with performance 
needs.

-- 
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

  reply	other threads:[~2010-10-26 22:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25  5:26 XFS journaling position klonatos
2010-10-25 16:10 ` Geoffrey Wehrman
2010-10-26 22:27   ` Michael Monnerie [this message]
2010-10-26 23:28     ` Dave Chinner
2010-10-26 23:59       ` Michael Monnerie
2010-10-27 14:27     ` Robert Brockway
2010-10-27 14:32       ` Robert Brockway
2010-10-28  9:44         ` Michael Monnerie
2010-10-28 23:33           ` Stan Hoeppner
2010-10-29  7:58             ` Michael Monnerie

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=201010270027.26687@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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