I continue to use: https://gitlab.com/mailman/mailman/-/merge_requests/1129 to reduce the memory footprint of mailman upon start-up (when only one processor is available). Within the past month some other code change that was made conflicts with this, but unless you are running a bleeding edge version this should still work.

Nelson

On 6/6/24 07:45, Marc SCHAEFER wrote:

Hello,

It seems the mailman & mailman-web memory footprint are somewhat big. It looks a lot of instances are started.

I have seen this:https://gitlab.com/mailman/mailman/-/issues/1050 and added this to the end of /etc/mailman3/mailman-web.py:

Q_CLUSTER = { 'workers': 2, 'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5, }

However, it does not seem to really reduce the memory footprint.

Any other suggestions?

Thank you.

---

Mailman-users mailing list --mailman-users@mailman3.org To unsubscribe send an email tomailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

This message sent tojustfixit@marilynstrother.com