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
Cc: Ivan.Novick@emc.com, aelder@sgi.com
Subject: Re: [RFC, PATCH 0/2] xfs: dynamic speculative preallocation for delalloc
Date: Fri, 15 Oct 2010 09:14:54 +0200	[thread overview]
Message-ID: <201010150914.55604@zmi.at> (raw)
In-Reply-To: <C8DCC927.48D3%ivan.novick@emc.com>


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

On Donnerstag, 14. Oktober 2010 Ivan.Novick@emc.com wrote:
> I have seen ~50% performance improvement in read rate when changing
> from small extents to large extents with XFS. Essentially going from
> not using allocsize to setting 1gb allocsize.  Also GB/s class
> filesystem.

In case of a database, I'd say 1GB allocsize seems fine. But when you're 
at /var/log/, it could be a penalty, as when you have 50 open log files 
which get permanently appended, you have 50GB preallocated which almost 
surely won't be needed before the log is rotated anyway.

The question is: what is a good value for preallocation?

I'd guess for a database 1GB seems reasonable, for /var/log one full 
stripe (nr-data-disks * stripe size), for webserver/ftp data too, as 
well as a fileserver (storing office documents) and mailserver (storing 
each mail as a separate file or into one flat file).
Or, when you have an app that writes files of specific size, use the 
"normal maximum" file size. We have a special server storing files of 
normally 50M-1G size, there I set allocsize=1024k, so that files will be 
in one junk on disk. When sometimes a file is bigger, then it will be 
fragmented but at reasonable sizes so it won't matter too much.

Is that reasonable?

Are there guides to help with that? I'd like to write a FAQ entry if 
there is (can ever be?) a consensus of what would be a good value.

-- 
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-15  7:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 10:13 [RFC, PATCH 0/2] xfs: dynamic speculative preallocation for delalloc Dave Chinner
2010-10-04 10:13 ` [PATCH 1/2] xfs: dynamic speculative EOF preallocation Dave Chinner
2010-10-14 17:22   ` Alex Elder
2010-10-14 21:33     ` Dave Chinner
2010-10-15  6:51       ` allocsize mount option, was: " Michael Monnerie
2010-10-15 11:59         ` Dave Chinner
2010-10-04 10:13 ` [PATCH 2/2] xfs: don't truncate prealloc from frequently accessed inodes Dave Chinner
2010-10-14 17:22   ` Alex Elder
2010-10-14 21:28     ` Dave Chinner
2010-10-14 17:22 ` [RFC, PATCH 0/2] xfs: dynamic speculative preallocation for delalloc Alex Elder
2010-10-14 21:16   ` Dave Chinner
2010-10-14 21:50     ` Ivan.Novick
2010-10-15  7:14       ` Michael Monnerie [this message]
2010-10-15 11:45         ` Dave Chinner
2010-10-17 14:31           ` Michael Monnerie
2010-10-17 23:49             ` Dave Chinner
2010-10-18  6:39               ` 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=201010150914.55604@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=Ivan.Novick@emc.com \
    --cc=aelder@sgi.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