Re: ext4 unlink performance

[Bruce Guenter <lists-linux-ext4@bruce-guenter.dyndns.org>]

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

On Thu, Nov 13, 2008 at 02:46:28PM -0500, Theodore Tso wrote:
> I'm assuming that ext3 filesystem was created with htree enabled
> (possibly not true on older versions of e2fsprogs), but if you're
> creating ext4 filesystems, I'm assuming that you have been using an
> 1.41.x version of e2fsprogs.

All filesystems are new filesystems, created with e2fsprogs 1.41.2, all
with the default options except for ^huge_file and the inode size.

> If this the the case, the most likely explanation is that that ext4
> defaults to barriers enabled, and ext3 defaults to barriers disabled.
> So try mounting ext3 with "-o barriers=1", or ext4 with "-o
> barriers=0", so that the comparison is between apples and apples.

The indication from dmesg is that ext4 is already running with barriers
disabled due to running over dm, but I will re-run with barriers forced
off to double check.

-- 
Bruce Guenter <bruce@untroubled.org>                http://untroubled.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]