On Sat, Oct 11, 2025 at 5:10 PM Stephen J. Turnbull <steve@turnbull.jp> wrote:
Odhiambo Washington via Mailman-users writes:
Using the uwsgi.ini from the virtualenv method documentation, mailmanweb is constantly using 2GB RAM on my server.
Do you mean only HyperKitty + Postorius? That seems like a lot. My experience is that even on an insanely heavily loaded server (20k+ lists) the whole suite uses about 2.0G. Since on that server, Mailman core was forking 22 processes at ~83MB each (very little shared, not sure the technical reason for that, maybe the Python heap just can't be shared?), core was taking up about 1.8G. HyperKitty and Postorius took a little more (I don't recall exactly, maybe 250MB?)
Yes, just Hyperkitty+Postorius: Please see https://imgur.com/a/LPAY69N It represents what I see daily when I run btop.It's always around 2GB, but rarely do I see above. I only have 1 major active mailing list on this server. There are other inactive ones. The main ML has been active since 2005. I migrated it to MM3 from MM2.1.39.
My more standard setup (that one had like 2 IN queue slices and 8 OUT queue slices) I ran Mailman suite + PostgreSQL (dedicated to Mailman)
- Postfix + nginx (also mostly dedicated to Mailman) + Cyrus IMAPd in a nominal 2GB Digital Ocean droplet. It didn't run "comfortably", adding any serious load that chewed up 100s of MB RAM would get things OOM-killed, but 2GB total (including kernel and all) was barely enough for that system in normal situations.
My database (MariaDB) size is 2GB.
Do you mean in memory or on disk? Either way that should have ~0 effect on the size of the Mailman core and web processes.
My MM3 database size on disk.
Is this expected?
Depends on if you mean exactly what you said ("mailmanweb"). If so, no, I would expect mailmanweb (only) to run in 500MB easily and probably be OK in 250MB. If you mean "when I start Mailman and mailmanweb, memory usage jumps by about 2GB", then yes, that's what I'd expect.
In my case, the ~2GB RAM consumption by the uwsgi process is a constant.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]