On Mon, May 27, 2002 at 03:16:43PM -0400, Barry A. Warsaw wrote: > There are a lot of unknowns here though. For example, we don't know > if your rate limits are caused by MTA or network throttles. If your > server is idle then i/o is suspect but we don't know if creating more > outgoing qrunner processes would help you (by splitting up the queue > hash space among parallel processes). Is your MTA spooling to the > same filesystem that Mailman is spooling off of? If your MTA is > throttling and it's running synchronously with the outgoing qrunner > then Mailman may just be sitting around blocked on output to your > MTA. Or maybe your disk subsystem can't take the pressure of Mailman > reading off of it while your MTA is writing to it. What happens if > you put them on different disks and/or controllers? And what effect > does using some other filesystem (e.g. reiserfs) have on throughput?
Hmmm... suggestion for future point releases: having some instrumentation that would make it easier to decide where the throttles *are* would be Really Useful. Mailman has lots of *configuration* knobs, but few *runtime* knobs, that I've seen, and almost *no* meters. It's a Subsystem; it needs that stuff. Cheers, -- jra -- Jay R. Ashworth [EMAIL PROTECTED] Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman-21/listinfo/mailman-developers
