From: Dave Chinner <david@fromorbit.com>
To: Sami Liedes <sliedes@cc.hut.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext4 is faster with LVM than without, and other filesystem benchmarks
Date: Sat, 8 May 2010 08:46:30 +1000 [thread overview]
Message-ID: <20100507224630.GC25419@dastard> (raw)
In-Reply-To: <20100507142310.GF13143@lh.kyla.fi>
On Fri, May 07, 2010 at 05:23:10PM +0300, Sami Liedes wrote:
> Basically the directory hierarchy consists of
>
> * directory backuppc/cpool - a pool of compressed backed up files
> - The individual files are of the form
> backuppc/cpool/f/1/d/f1d2d2f924e986ac86fdf7b36c94bcdf32beec15
> - There are some 456000 files in the pool, all hashed by their
> SHA256 sum
> - These take the first about 490 gibibytes of the archive
>
> * directory backuppc/pc with individual backups of a few machines
> - Essentially contains the root filesystems of quite normal desktop
> Linux machines.
> - All backed up files are hardlinks to the pool.
> - Files with size 0 are not hardlinked but represented as themselves.
> - Contains some 10.4M hard links to files in the pool, interspersed
> with some 84300 empty files and very few regular files
>
> The benchmarks were all I/O-bound on the speed of the target
> filesystem and partition. This was achieved by making a copy of the
> tar that has all the file contents zeroed and using a fast compressor
> (lzop) so the decompression of the .tar.lzop was still easily
> target-disk-bound.
[...]
> On XFS, extracting the archive took more than 16 hours (58548 seconds;
> only one sample), so XFS performs rather poorly in this I assume quite
> pathological case.
Not pathological, but XFS is generally slower at creating and
removing large numbers of files compared to ext and btrfs until you
get to parallel workloads and expensive storage hardware. However,
just adding the "logbsize=262144" mount option should speed it up
significantly for this workload.
FWIW, how big is the compressed tarball you are extracting? If it's
not large, can you make it available somewhere? I've current got a
set of pending modifications to XFS(*) that should help this
workload and this looks like a good load for testing...
Cheers,
Dave.
(*) http://oss.sgi.com/archives/xfs/2010-05/msg00060.html
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2010-05-07 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 14:23 ext4 is faster with LVM than without, and other filesystem benchmarks Sami Liedes
2010-05-07 15:28 ` Bernd Eckenfels
2010-05-07 17:49 ` Eric Sandeen
2010-05-07 22:46 ` Dave Chinner [this message]
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=20100507224630.GC25419@dastard \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sliedes@cc.hut.fi \
/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