On Oct 29, 2009, at 11:54 AM, Mark Sapiro wrote: > If I understand the OP's situation, this probably won't help. I think it > is a case of a single post to a large list. In this case, a single > OutgoingRunner will handle the message and the other runners will do > nothing.
If it's a case of a single post to a large list, then the problem is most likely going to be Python pickle contention. Split the large list up into multiple smaller sub-lists, with a parent "umbrella" list. More info on that solution is in the FAQ wiki, but the OP should have already found that if they searched for "performance". I can guarantee you that I can build an MTA configuration that is faster than Mailman could ever possibly be, for this single reason alone -- even if you run both on a pure RAMdisk. As for the rest, an option would be to use a load-balancing switch (either hardware or implemented in software), but there's a heck of a lot of tuning to be done on a single machine running a properly configured MTA and a properly designed mailing list server infrastructure, before you get to the point where load balancing switches and multiple outbound mail relay servers would start to make a big difference. Most of these topics are at least touched on in the FAQ Wiki and the fact that the OP hasn't mentioned them tells me that they either didn't do their homework, or they don't understand the concepts well enough to be able to do the homework. -- Brad Knowles <bradknow...@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu> ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
