Ofer Inbar:
> Wietse Venema <[EMAIL PROTECTED]> wrote:
> > > see clearly in the logs that each one of them is still taking several
> > > incoming messages per second at peak times, and cleanup is placing
> > > them all in the incoming queue, and the incoming queue gets very big.
> > > in_flow_delay is apparently not trigerring.
> > 
> > in_flow delay does not prevent the queue from growing. I don't
> > understand where you get this idea from.
> 
> I did not get this idea at all.

"incoming queue gets very big" implies that you were expecting
the queue to remain below some size.

> What I expected to see, however, is that when in_flow_delay were
> trigerred, each smtpd process would not be taking in multiple messages
> per second.  Seeing that they were taking in multiple messages per
> second (per process ID) when I have in_flow_delay=10s is why I said
> "in_flow_delay is apparently not trigerring"

Postfix can accept up to 20000 messages before in_flow_delay
triggers.  That's just the queue manager pulling mail from the
incoming queue into the active queue.  At this stage, inflow delays
happen only when you overload the disk to the point that the queue
manager can't keep up.

If your measurement is based non-equilibrium behavior, then the
measurement is invalid.  in_flow_delay has effect on a sustained
flow of mail, not on burst of order 20000.

        Wietse

Reply via email to