On 2023-04-06 18:47, Per Jessen wrote:
Christian Boltz wrote:
Hello,
...
Feeling all good about having achieved something worthwhile, I decided to attack poo#102203 - about uwsgi/gunicorn memory usage. On my Google travels, I came across some mention of python memory leaks ........ In the eternal words of Charlie Brown, see attached.
Long story short - by making gunicorn processing threads restart every X requests, mailman3 memory usage took a dive, olympic style. Instead of random processes being oom killed every day, mailman3 is now trundling along with 9Gb of free memory and largely unused swap.
who are these incompetent programmers that cannot fix simple memory leaks? having to regularly restart is something I reluctantly resorted to thirty-odd years ago, and even then it worried me. <endof/>
If I recall correctly, "spamd" reloads every few mails, maybe after a single one, not only for memory reasons. /etc/sysconfig/spamd: SPAMD_ARGS="... --max-conn-per-child=1" Doesn't seem to be the default nowdays, though. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)