On 30/03/13 21:57, Chris Steipp wrote:
I would agree with that, and add that spam fighting
(AbuseFilter, Spam / Title blacklist, etc) are some of the highest
consumers of cpu for each wikipedia edit. So too much spam protection
and you'll be right back where you're at with cpu. So you definitely
want to do some profiling, and make sure you're addressing the biggest
Very good point. Some of your anti-spam measures may be taking a good
chunk of CPU.