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

Khalid Baheyeldin kb at 2bits.com
Fri Jan 31 18:39:40 EST 2025


On Fri, Jan 31, 2025 at 6:28 PM Ronald Barnes via kwlug-disc <
kwlug-disc at kwlug.org> wrote:

> Khalid Baheyeldin wrote on 2025-01-31 05:11:
>
> > 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.
>

PostgreSQL itself will be using a lot of memory.

But my guess here is that it could very well be that processes that issue
queries to the database do it in an inefficient way.

For example, if they do a query that returns a very large dataset, and then
process it using Python code, in memory to further whittle it down to what
it is needed.

This is one of the things that are not obvious to many (most?) developers,
specially if they are using an abstraction layer that masks all this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20250131/e2414fba/attachment.htm>


More information about the kwlug-disc mailing list