[OGDev] [OpenGuides-Dev] OG performance

[Paul Makepeace]

A follow-up on a 2.5yr-old mail from your London OG admin,

OpenGuides London is frequently bursting 100% of a 3Ghz HT CPU which is
causing stix (the server) load problems,

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                  
11060 www-data  19   0 18940  15m 2576 R 26.5  1.5   0:00.80 index.cgi
11040 www-data  19   0 21420  17m 2612 R  6.9  1.7   0:01.12 index.cgi
11039 www-data  19   0 21004  17m 2584 R  6.6  1.7   0:01.04 index.cgi
11048 www-data  19   0 21392  17m 2612 R  6.6  1.7   0:01.10 index.cgi
11051 www-data  19   0 21248  17m 2612 R  4.6  1.7   0:01.02 index.cgi

This CPU's nearly twice as fast as the server's the hosting was on when
I last wrote this (the IO yet faster) and not using supersearch.cgi has
obviously helped, all of which has bought some time, retrospectively. Some
plan however to make use of mod_perl or other CPU-reduction measure
needs to come into effect pretty soon.

What say ye?

P

Je 2004-10-21 17:25:59 +0100, Paul Makepeace skribis:
> Hi, I don't follow OG development but as host operator a few things are
> coming up. The machine's load is gradually climbing over time and some
> of that is OG.
> 
> Despite a relatively low hit rate on OG it is consuming quite a bit of
> resource. If OG started taking off it would take the machine down.
> 
> First up: index.cgi requires 0.35s to perform a `perl -c` syntax check.
> Any thoughts on putting OG on a mod_perl server? I have mod_perl running
> here of course and we'd need to coordinate some apache.conf stuff.
> 
> Second: the supersearch.cgi gulps down CPU, often for seconds at a time.
> It is a frequent resident of `top` output. This isn't really
> acceptable. I'm going to request this feature be turned off unless an
> effective optimisation plan or some other way to reduce its impact
> here is constructed pretty soon. Sorry about this but it's encroaching
> on others.
> 
> Third: I wonder if there's some way to instruct robots not to spider
> parts of your wiki. This ought to speak for itself:
>   $ grep crawl /var/log/apache/london.openguides.org-access.log | grep 'action=edit' | wc -l
>   8242
>   $
> 
> Finally: I posted about a DoS and was wondering what the status of a
> solution was. http://openguides.org/mail/openguides-dev/2004-October/000542.html
> 
> Cheers,
> Paul (any overbearing tone unintentional ;-)

--