From: Andrew Morton <akpm@osdl.org>
To: Ron Peterson <rpeterso@mtholyoke.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2/3 files per directory limits
Date: Wed, 23 Feb 2005 20:39:15 -0800 [thread overview]
Message-ID: <20050223203915.1c10ceb1.akpm@osdl.org> (raw)
In-Reply-To: <20050224031107.GA8656@mtholyoke.edu>
Ron Peterson <rpeterso@mtholyoke.edu> wrote:
>
> I would like to better understand ext2/3's performance characteristics.
>
> I'm specifically interested in how ext2/3 will handle a /var/spool/mail
> directory w/ ~6000 mbox format inboxes, handling approx 1GB delivered as
> 75,000 messages daily. Virtually all access is via imap, w/ approx
> ~1000 imapd processes running during peak load. Local delivery is via
> procmail, which by default uses both kernel-supported locking calls and
> .lock files.
>
> I understand that various tuning parameters will have an impact,
> e.g. putting the journal on a separate device, setting the noatime mount
> option, etc. I also understand that there are other mailbox formats and
> other strategies for locating mail spools (e.g. in user's home
> directories).
>
> I'm interested in people's thoughts on these issues, but I'm mostly
> interested in whether or not the scenario I described falls within
> ext2/3's designed capabilities.
>
noatime will help.
increasing the journal size _may_ help.
With 6k files per directory you'll benefit from indexed directories
(htree). Use `tune2fs -O dir_index'. dir_index isn't available for ext2.
prev parent reply other threads:[~2005-02-24 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 3:11 Ron Peterson
2005-02-24 3:24 ` Joel Jaeggli
2005-02-24 4:18 ` Lee Revell
2005-02-24 4:39 ` Andrew Morton [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=20050223203915.1c10ceb1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@mtholyoke.edu \
/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
all inboxes | Powered by JetHome®