On 3/5/19 8:26 PM, @lbutlr wrote:
On 05 Mar 2019, at 13:50, Mayhem <mayhe...@gmail.com> wrote:
I also have nginx/apache and sql running on the same dedicated machine,
There will use much more of your system that all of postfix, including your
dovecot (or whatever), and the DNS lookups are a minuscule portion of what
postfix does.
My very low-spec machine occasiaonly sees a single IMAP process as high as
0.12% and master might be at 0.05%. Heck, my logging system used more resources
than Postfix does.
CPU: 0.5% user, 0.0% nice, 0.6% system, 0.0% interrupt, 98.9% idle
Try running top -Sz (or top -c a, depending on your system.top version) on your
system and see what is using a lot; bet you find it is perl (assuming you are
running spamassassin).
I would agree. I've been running Postfix and hosting a few domains for
a very long time. Postfix is never the resource hog. MySQL, and all
the things that go with tearing a message apart and checking it for
viruses is what eats up all the CPU. That and systemd anything. If
you're having trouble with DNS lookups I would disable systemd-resolved
and replace it with something faster for recursion. systemd my also try
to bypass your resolvers for resolvers hard coded into the software.
Those are Google public DNS and Cloudflare public DNS, both of which are
slow. So is systemd. I've been running pdns recursor (very, very fast)
and low on resources. pdns recursor queries the root servers directly,
not through several layers.
DNS has become very ugly as Google and Cloudflare attempt to monopolize it.
--
Best Regards
Curtis Maurand
mailto:cur...@maurand.com
