[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.
>
> 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.
>
> Regards,
>
> Simon E.
I've had good luck with some rate limiting tricks.
1) Inject 500 messages then wait 2 seconds. This seems to give
qmail-send time to process the 500 messages and kick off more
qmail-remotes before it has to deal with the next 500 new messages.
2) Call qmail-queue directly, saves on one fork/exec
3) have the perl script monitor the size of the queue. Slow down
the rate of injection if the queue gets above 10K or if the
todo gets above 2K. Qmail's ability to fork qmail-remote
processes drops when the inode trees get large.
Ken Jones
inter7
