On Fri, 10 Dec 1999 20:15:06 +0100 , Markus Stumpf writes:
[triggering slows down qmail]
> This causes qmail to deliver in "waves".
>
> I have graphically documented this (avail at
> <URL:http://www.lamer.de/maex/creative/software/qmail/deliver-stats.gif>
> and also asked on the list whether there is a workaround for this,
> but it looks like there isn't.
[snip]
> One way to somewhat overcome this on a "bulk only" mailserver, where it's
> not too important that you have quick notice on new messages is to
> chmod 000 /var/qmail/queue/lock/trigger
> That way qmail has no communication with qmail-queue and checks for
> unprocessed messages only each 20 minutes.
Actually, 25 (in my copy, anyway).
> Thus the bounces don't come in the way of deliveries, so deliveries are
> highly concurrent.
> However this is no solution for a "default" mailserver.
>
> Any comments on this analysis?
I think that the "no-trigger" idea has some merit,
even for general purpose servers. I will have to
try this out myself, but it would seem that reducing
SLEEP_TODO in qmail-send.c, and removing the trigger
mechanism should eliminate the starvation caused by
rapid triggering.
--
Chris Mikkelson | Quidquid latine dictum sit, altum viditur
[EMAIL PROTECTED] |
