> -----Original Message-----
> From: pgsql-www-owner@postgresql.org
> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Marc G. Fournier
> Sent: 05 June 2004 15:19
> To: pgsql-www@postgresql.org
> Subject: [pgsql-www] Just to give an idea ...
>
>
> Top ten processes on mars (where pgfoundry and archives are located):
>
> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
> www 41463 17.3 0.1 12364 5808 ?? SJ 11:00AM
> 0:05.75 /usr/local/sbin/httpd
Ignoring mars and considering jupiter which is suffering from similar
problems (which you told me is not the database as I had suspected),
what do you think is actually causing this excess load? None of the
backend web code should be sufficiently complex to see the sort of loads
we seem to be seeing, even under the load the site gets. I've
apache-benched far more complex stuff on far less hardware and not
suffered like this. Geez, the vast majority of our PHP code simply does
include()'s and echo()'s, and even that only normally gets executed once
per hour - the users read static html for the most part!
I can only imagine that somewhere in the code there is a serious error
that is causing this... Or jupiter is actually a Sinclair ZX Spectrum
:-)
/D