archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <>
Subject: Re: [benchmarks] various filesystems on 2.5.68
Date: 24 Apr 2003 15:31:22 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20030424124728.GA1477@rushmore.suse.lists.linux.kernel> writes:

> mount options
> mount -t ext2 -o defaults,noatime /dev/sdc1 /fs1
> mount -t ext3 -o defaults,noatime,data=writeback /dev/sdc1 /fs1
> mount -t reiserfs -o defaults,noatime /dev/sdc1 /fs1
> mount -t jfs -o defaults,noatime /dev/sdc1 /fs1
> mount -t xfs -o logbufs=8,logbsize=32768,noatime /dev/sdc1 /fs1
> mkfs command
> mke2fs -q /dev/sdc1
> mke2fs -q -j -J size=400 /dev/sdc1
> yes  "y" | mkreiserfs /dev/sdc1 >/tmp/mkr.out 2>&1
> jfs_mkfs -q /dev/sdc1
> mkfs.xfs -l size=32768b -f /dev/sdc1
> Very recent version of xfsprogs/jfsutils/reiserfsprogs/e2fsprogs.
> XFS mount/mkfs options came from the XFS FAQ and are very desireable
> for these tests based on an earlier run without them.  If anyone

It's my experience too that XFS often performs badly with the default
mkfs/mount options, especially for metadata intensive workloads. The
drawback is that it eats memory. I've been thinking about making it
set the bigger mount option by default based on the available physical
memory; this would probably help a lot of users.

iirc one drawback is that it eats from the vmalloc area which is only 64MB 
by default on 32bit.  But still should not be that big an issue. On 64bit
it's not an issue at all of course.

Of course the log size cannot be changed this way, but perhaps the default
in mkfs is just too small for today's disk sizes?


       reply	other threads:[~2003-04-24 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030424124728.GA1477@rushmore.suse.lists.linux.kernel>
2003-04-24 13:31 ` Andi Kleen [this message]
2003-04-28 21:41 [benchmarks] various filesystems on 2.5.68 rwhron
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24 12:47 rwhron
2003-04-28 12:53 ` Hans Reiser

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).