On Mon, Dec 03, 2012 at 01:54:44PM -0500, Kevin A. McGrail wrote: > > I've added two tricks to this filter. > > One, I pass the load_avg to the filter and use it to modify the size > limit for spamc based on load. The lower the load, the higher the > multiplier.
Seems kind of pointless. Have you actually measured how larger messages affect cpu usage? Especially since usually there are much less messages the larger they get. If 10% more cpu or whatever makes your server hang, then you have other problems. :-) > Two, I'm trying a system that also truncates messages mid-message at > the threshold to scan them anyway. > > The second idea has been pretty controversial but I think the first > one is a neat idea. Why is it controversial? Amavisd-new 2.6.3 had this feature since 2009, so it's used probably very widely - even without users knowing it. I've never seen any ill effects. > This might be something neat to add to spamd/spamc natively where > there is a load average multiplier concept. Thoughts? Load average is quite silly measurement. The maximum depends on the number of cpu cores/threads. Also this kind of limiting makes sense only on a pre-queue filter in which case such "throttles" should be applied way before anything gets to SA.
