Skip to contentSkip to conversation

ext2/3 files per directory limits

DISCUSSION Ron Peterson 4 participants 4 messages Feb 24, 2005

lore
Share & tools
lore
#0 lore raw

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.

Best.

Signature · 4 lines
Ron Peterson
Network & Systems Manager
Mount Holyoke College
http://www.mtholyoke.edu/~rpeterso
#1 lore raw
Quoted 8 lines · Ron Peterson

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.

At some point it makes sense to subdivide you mail load because serialization of i/o on that one filesystem becomes a bigger issue than the performance of your filesystem... We deliver into mbox formatted mailboxes inside users homedirs, some folks do a similar thing with maildir. In the end you can on make one filesystem so fast. beyond that you need more filesystems to acheive any kind of reasonable scaling...

Quoted 13 lines

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.

Best.

Signature · 1 line
-------------------------------------------------------------------------- Joel Jaeggli  	       Unix Consulting 	       [email protected] GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2
#2 lore raw
In reply to Ron Peterson
Quoted 15 lines · Ron Peterson

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).

Quoted 3 lines

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.

Yes, ext2 and ext3 can handle that load easily. You should not have to do any special tuning.

The real question is why in the world you would want to use mbox format for this. It simply does not scale. Use maildir.

Lee

#3 lore raw
In reply to Ron Peterson
Quoted 16 lines · Ron Peterson

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).

Quoted 4 lines

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.