Gordon Messmer wrote:
Dan Melomedman wrote:
One problem with that design is that it scales poorly. Very poorly. Especially when your filters are python or perl scripts, and you have to start the interpreter, parse scripts, and load modules for every individual message that comes in to the server.
Scales just as well or better than spamassasin for instance
Which is why they introduced "spamc". Spamassassin by itself scales horribly.
, as I am using qmail-qfilter now. For performance, you could always write those as fast C modules.
Wait. You want to redesign the courier submission process to be a pipeline of filters so that filters can be written more easily (none of this unix socket stuff, you said), but you suggest that for performance they should be written in C?
/me boggles
Also, my perl is linked -static. It's still a simpler, and more user-friendly design.
Linking perl statically won't help much. It still has to go through a whole lot of initialization, module loading, and script parsing.
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
