"David Harris" <[EMAIL PROTECTED]> writes:
| He says that Maildir is unsuitable for large servers because the filesytems
| serialize creation and deletion of files in a single file system, because
| the inode and free block tables have to be manipulated. Thus the file
| creation part of Maildir drivery ends up being serialized and you spend all
| your time in the filesystem. He states problems with servers processing more
| than a few hundred messages per second (300+ or so).
|
| Anybody else have some experience with this?
300 * 60 * 60 * 24 == 25,920,000. Did Mark actually measure a single
mail server doing 25M deliveries per day? I don't think that's a bad
figure.
My humble opinion: Not everyone puts their entire enterprise on one
mail server. Many mail systems serve department sized units, and they
aren't asked to deliver anything remotely approaching 25M
messages/day. For this population, Mark's concerns are totally
irrelevent. The purpose of Maildir is to serialize operations without
recourse to flock, and to enable safe operation over NFS. Mark rejects
NFS a-priori, but most department sized outfits use NFS for everything,
and so maildir can be a huge win.
