Thanks guys.
> So you definitely want to do some profiling, and
make sure you're
addressing the biggest issues first.
I havent done profiling before. I'm assuming this is the link to check out:
http://www.mediawiki.org/wiki/Manual:How_to_debug#Profiling
I will attempt to do this next time I have CPU problems.
Right now we are running really well on Linode (except for that one time a
few weeks ago where it went up to 160% usage). I have to again thank the
people who helped me with that advice before. I'm so happy with the speed.
Linode recently increased their 512MB ram package to 1GB (doubled for all
packages).
thanks
Dan
On Sun, Mar 31, 2013 at 4:22 PM, Platonides <Platonides(a)gmail.com> wrote:
On 30/03/13 21:57, Chris Steipp wrote:
I would agree with that, and add that spam
fighting tools
(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
issues first.
Very good point. Some of your anti-spam measures may be taking a good
chunk of CPU.
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l