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: Norbert Veber <nveber@pyre.virge.net>
Subject: Re: Small files perform much faster on newly formatted fs?
Date: Thu, 9 Jun 2011 07:44:12 +0200	[thread overview]
Message-ID: <201106090744.18277@zmi.at> (raw)
In-Reply-To: <20110608185844.GB28625@pyre.virge.net>


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

On Mittwoch, 8. Juni 2011 Norbert Veber wrote:
> I re-created the test filesystem to be the same size (20gb) as the
> original, and copied all the same files to it, so both are now 80%
> full.

But copying data at once leads to "perfectly" aligned data, and cannot 
be compared to a filesystem that has aged over the years. Maybe you can 
compare it like this:
1) remount the old partition with "noikeep"
2) mv /old/* /new
3) cp /new/* /old/

Maybe that would help? I'm interested to find the difference.

Also, as Eric said, both partitions are on different locations on the 
disks, but I guess your old partition is more outside, thus in the 
quicker region, than the new partition. Is that true?

Could it be that the old filesystem gets mounted with different 
logbufs/logbsize values? Would the mount options 
"logbufs=8,logbsize=256k" maybe make a difference?
Is the position of the log area fixed on disk? Maybe that is not stripe 
aligned. Could you check with a newer kernel using "delaylog"?

[Dave wrote]
> Those mount options are ignored if the filesystem doesn't have the
> superblock feature bit set for aligned allocations. A filesystem
> with 0/0 for sunit/swidth does not have the superblock bit set....

And I guess it's not possible to set that bit now?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

// Haus zu verkaufen: http://zmi.at/langegg/

[-- 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:[~2011-06-09  5:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 16:37 Small files perform much faster on newly formatted fs? Norbert Veber
2011-06-08  7:11 ` Michael Monnerie
2011-06-08 12:26   ` Norbert Veber
2011-06-08 13:47     ` Michael Monnerie
2011-06-08 18:58       ` Norbert Veber
2011-06-09  5:44         ` Michael Monnerie [this message]
2011-06-08 20:52     ` Eric Sandeen
2011-06-08 21:16       ` Eric Sandeen
2011-06-09  1:29     ` Dave Chinner
2011-06-09  8:22       ` Christoph Hellwig
2011-06-09 13:48       ` Norbert Veber
2011-06-09 16:30         ` Michael Monnerie
2011-06-09 20:30           ` Norbert Veber
2011-06-09 21:17         ` Dave Chinner
2011-06-10  0:54           ` Norbert Veber

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=201106090744.18277@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=nveber@pyre.virge.net \
    --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