-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sep 30, 2006, at 9:36 PM, Tokio Kikuchi wrote:
With the current default method of invoking mailman post program
and pipelineing takes 49 seconds for the last 100th message to
reach the list member (a local user), while maildir and lmtp
interface reduce this time to 15 or 16 seconds. You can also see
most of the difference occured in MTA's In and Out, which means
execution of mailman post program is the most heavy load. Also,
maildir and lmtp passing of message from MTA to mailman is a
relatively small task than the processing the list message like
cooking headers and appending footers and all like those.Conclusion: Maildir or LMTP will not likely be a bottleneck.
Those are very interesting number Tokio, thanks for doing the
experiment and posting there results. How much work is your LMTP
implementation doing when it receives the message? Is it parsing it
and storing the msg pickle? Is it touching any MailList objects?
Does it do the entire delivery pipeline? IIUC your results indicate
total throughput from submission to MTA to final delivery to user.
If that's the case, there's some common constant amount of work being
done and I'm just wondering how efficient the LMTP part will be.
When you feel confident about your lmtp implementation, go ahead and
check it in (probably in Mailman/bin/lmtp.py with hooks for mmshell
-- or I can do the latter). I think at this early date we should
make both LMTP and Maildir delivery possible, then we'll try to get
real-world feedback from users as to which we should ultimately
recommend.-Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRR/eWHEjvBPtnXfVAQJLPAP/cmQEXjI3fx3Sj4Yq8QJhT4DChuAAVWF8 y0jiCLpViWRP67QtXkEmJhKJPsoakgfQZXMnENHNUzlQ2321KO1Ed4S4H0eKRhWJ DU8KeudwfDzobA42duaWBL6412RNZlmE+b8mEWtctX5ESM3YhHbELklGCdB8GPAV oSRhMsQGJbY= =IA1i -----END PGP SIGNATURE-----