[Mailman-Developers] High memory usage of MailMan 2.1's runners
jplist at kiwigeek.com
Fri Feb 6 11:39:03 EST 2004
I run a reasonably active mailing list service, with a fair number (read >
20) lists with subscriber numbers in the range of anywhere from 5,000 to
We are currenty migrating from an existing Majordomo service (That'd be
another 20 lists to go to Mailman), and are pleased with how friendly
Mailman seems to be with customers, not to mention configurable.
Unfortunately Mailman seems to be a fairly serious resource hog. The CPU
spikes I can handle, I realise that when you're churning out 50,000 mails
you need a little processing power - but the memory usage seems a little
When the mail starts a flowin', the memory starts a goin'.
Currently I've had mailman running for 5 hours, and clearly have had a
couple mailing lists go out - because Mailman is sucking up 405MB of
memory. The worst culprits are BounceRunner with 56MB, IncomingRunner and
VirginRunner with 105MB a piece and the OutgoingRunner with 112MB.
I've seen mention of performance issues that most seem to be saying is
just part of Mailman - but this seems a little silly. What suggestions do
you folks have for relieving this... Is there much I can do?
This seems highly suggestive of a memory leak somewhere, I can't imagine
it should ever use this - and given I would call this a Bad Thing - what's
on Mailmans plate in the future to alleviate this?
Thanks for the insight;
More information about the Mailman-Developers