[kwlug-disc] Service resource management: i.e. Mailman3 vs Mailman2

Khalid Baheyeldin kb at 2bits.com
Wed Feb 5 09:04:36 EST 2025


But if I was the one investigating this, I would be interested in
things like: are all the processes large, or just a few? That would
tell me if there is a common library that is included in all processes
that has the bloat, or that is not the case.

>From what you said:
> The RSS columns are roughly 6× higher on a freshly started MM3 vs a
> long-running MM2.

It seems that the memory bloat is across the board.

You can also simplify things further, with only the memory and process:

ps -eo rss,args | grep python | sort -nrk1 | less

That would sort the processes by their resident set size, descending.

Also, the total used memory can be done using awk.
Having this built in systemd is just more straight forward.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20250205/b878f2e7/attachment.htm>


More information about the kwlug-disc mailing list