On Thu, Nov 13, 2025 at 6:35 PM Stephen J. Turnbull <steve@turnbull.jp> wrote:
Hirayama, Pat writes:
I finally looked at the host (rather than the logs of each container) and realized that the oom-killer was killing django-admin.
[snip]
I have seen reports that uwsgi systems use a lot more memory than gunicorn systems. I don't have hands on to confirm or analyze why, though. I'm not sure using Whoosh (instead of Xapian, Elastic Search, or SOLR) is a good idea -- I found it to be *extremely* slow on initial indexing of a system with lots of archives migrated from Mailman 2, and I wouldn't be surprised if that uses a lot of memory (since then I have stuck to Xapian, so no confirmation or analysis).
I can attest to the fact that using gunicorn uses much less memory than
uwsgi.
On my server, I switched from uwsgi to gunicorn and the memory consumption
dropped drastically - to almost nothing!
Well, not nothing, but the constant 2GB that the mailman (uwsgi) process
was using suddenly disappeared from my btop radar.
-- 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]