Re: getdents - ext4 vs btrfs performance
- Subject: Re: getdents - ext4 vs btrfs performance
- From: "Ted Ts'o" <tytso@xxxxxxx>
- Date: Thu, 1 Mar 2012 13:42:48 -0500
- Cc: Chris Mason <chris.mason@xxxxxxxxxx>, Hillf Danton <dhillf@xxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, linux-btrfs@xxxxxxxxxxxxxxx, lczerner@xxxxxxxxxx
- In-reply-to: <CADDYkjRs934T2D7DPCk_dcrazptWtLu70=A61R32p22Ee1iXsw@mail.gmail.com>
- Mail-followup-to: Ted Ts'o <tytso@xxxxxxx>, Jacek Luczak <difrost.kernel@xxxxxxxxx>, Chris Mason <chris.mason@xxxxxxxxxx>, Hillf Danton <dhillf@xxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, linux-btrfs@xxxxxxxxxxxxxxx, lczerner@xxxxxxxxxx
- User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, Mar 01, 2012 at 03:43:41PM +0100, Jacek Luczak wrote:
>
> Yep, ext4 is close to my wife's closet.
>
Were all of the file systems freshly laid down, or was this an aged
ext4 file system?
Also you should beware that if you have a workload which is heavy
parallel I/O, with lots of random, read/write accesses to small files,
a benchmark using tar might not be representative of what you will see
in production --- different file systems have different strengths and
weaknesses --- and the fact that ext3/ext4's readdir() returns inodes
in a non-optimal order for stat(2) or unlink(2) or file copy in the
cold cache case may not matter as much as you think in a build server.
(i.e., the directories that do need to be searched will probably be
serviced out of the dentry cache, etc.)
Regards,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux NFS]
[Linux NILFS]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]