On Thu, Sep 07, 2000 at 11:13:04AM +1100, [EMAIL PROTECTED] wrote:
> My apologies for the last incomplete message
>
> Hi,
>
> Does anyone have some tips on getting peak performance out of mass
> mailings with qmail.
> We regularly send out newsletters to over 500,000 email address's on
> a weekly/fortnightly basis.
> I've looked through the archives and there are some excellent tips
> but I'm still hoping to push it further as a full mailout takes
> nearly a day.
>
> My current setup is qmail-1.03 with Russell Nelson's big-todo patch
> conf-split is set to 47
> concurrencyremote is set to 240
> We have written a simple perl script that takes the whole mailout and
> pipes it directly to qmail-inject
>
> The mailout flies with the concurrencyremote being hit after the pipe
> to qmail-inject is closed but it takes a long long long time for the
> qmail-inject process to finish.
How long is a "long long time"? What does vmstat show during the injection
process? Is it one qmail-inject with lots of Bcc:s? Or one qmail-inject
per recipient?
> Does anyone have any tips on how to analyse the performance
> bottle-necks .. disk / bandwidth etc ( this is a redhat linux 6.1
> box) or tips on a better way of doing this.
vmstat is a good place to start. What does it show during the delivery
process?
Are you running a local caching DNS server? Can I recommend djdns :>
Are you using multiple spindes? Can I recommend that you do.
Are you using a high performance logging system or are you using syslog? Can
I recommend multilog.
Regards.
