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

[Ronald Barnes]

Khalid Baheyeldin wrote on 2025-01-31 05:11:

> For htop, you can just sort (F6) by Mem or Res.
> One is total memory, including shared, the other is actual resident memory.
> You will immediately see what is taking up the most memory.

That's a good tip, thanks.


> I agree with Chris: searching and PostgreSQL seem to be the culprits.

The memory usage I showed earlier did not include PostgreSQL, it was a 
gazillion Python interpreters and one shell.



> Back to MM3, if the search is modular and can be turned off, that may do 
> it.

I don't remember how the indexing works, but I think it's triggered by a 
cron job or triggered by the archiving process.

i.e. the full text indexing takes at most one process and I don't think 
it's persistent.


All those Pythons are talking to Postfix, to each other, to PostgreSQL, etc.


I never really figured out how it does what it does, whether v2 or v3.

Looking now, I see a Python2 interpreter loaded thusly:

 > /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1

So, a NNTP gateway is loaded, consuming about 5MB RAM... for NNTP.

I can't find how to diable NNTP on Mailman v2.



Thanks for the top / htop tip!

I like btop for an overview but it might be a bit too busy sometimes.