Thanks again,
To give you a little insight, I load balance 3 of these for smtp.uconn.edu
So back when I saw the 20K limit it was just DNS round robin which is not real
load balancing.
I doubt latency of throughput will be significant enough that I notice it in
the future, my experience seeing issues was over 3 years ago.
[root@mta1 incoming]# tune2fs -l /dev/mapper/vg_mta3-lv_root |grep 'Filesystem
created'
Filesystem created: Tue Mar 19 13:58:16 2013
[root@mta1 incoming]# free -m
total used free shared buffers cached
Mem: 1877 1526 350 0 208 747
-/+ buffers/cache: 571 1305
Swap: 2015 193 1822
[root@mta1 incoming]# more /etc/redhat-release
Red Hat Enterprise Linux Server release 6.9 (Santiago)
-ANGELO FAZZINA
ITS Service Manager:
Spam and Virus Prevention
Mass Mailing
G Suite/Gmail
ang...@uconn.edu
University of Connecticut, ITS, SSG, Server Systems
860-486-9075
-----Original Message-----
From: owner-postfix-us...@postfix.org <owner-postfix-us...@postfix.org> On
Behalf Of Viktor Dukhovni
Sent: Tuesday, May 1, 2018 1:23 PM
To: Postfix users <postfix-users@postfix.org>
Subject: Re: postfix maximum load capacities by official document
> On May 1, 2018, at 12:50 PM, Fazzina, Angelo <angelo.fazz...@uconn.edu> wrote:
>
> Yes, I was guessing, must have be active and not incoming queue.
> Thanks for the explanation of what I was seeing.
I hope it is clear that the active queue size limits don't determine
the total number of messages Postfix can accept. Considerably more
mail might be sitting in "incoming" and "deferred".
On modern systems with lots of RAM you can also raise the active
queue limits from the default 20,000 to 100,000 or perhaps more.
Do it gradually and see how much memory qmgr(8) consumes.
More active queue space can help when most of the traffic is to
a small number of slow destinations, which can fill the active
queue and starve out other traffic.
--
Viktor.
