If you have a sufficiently equipped machine, why don't you install multiple
copies of qmail, each w/ its own concurrencyremote settings to the max?
This way you would have a large number of mails being sent out in parallel.
Set your script to inject to each queue separately.
Just make sure that the processes limit of your system allows this.
-makatao
"It is insufficient to protect ourselves with laws,
We must protect ourselves with mathematics."
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 07, 2000 8:13 AM
Subject: Mass Mailout Performance Tips
> 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.
>
>
>
>
