Bob C. Ruddy <[EMAIL PROTECTED]> wrote:
>
> Today was day two at my new job where they are rolling out a large, 5
> million email a day, qmail setup. There were some issues, but with changes
> to disk layout and some solaris tcp tuning, testing has been promising but
> needs more tweaking. Is there a set or rules or tunning characteristics to
> watch for for large email infrastructures?
I believe "Life with qmail" deals a little bit with large servers; qmail.org
also has a section about them.
Off the top of my head, the following suggestions have come up in the past
when dealing with large qmail installations, in no particular order:
-contract with Russell Nelson to provide _real_ advice :)
-throw Solaris in the bin. It's networking libraries are bloated and buggy,
and its filesystem performance sucks rocks.
-ensure the queue is on its own {disk, SCSI disk, 15kRPM SCSI disk, 15kRPM
SCSI RAID array)
-ensure logs are through multilog (not splogger/syslog) to a fast disk
-deliver locally to Maildirs on a NetApp Filer or similar high-performance
storage solution
-use big-todo and big-concurrency patches
-ensure you've got a dnscache running on the server for maximum DNS
performance
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
