On Sat, 5 Jun 2004, Dave Page wrote:
>
>
>> -----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!
k, www.* is on pluto, not on mars or jupiter, and tends to stay pretty
constant (occasional spikes) ...
jupiter isn't web related load, but mail ...
mars is a combination of things ...
note that the point of my point was that Josh's opinion appears to be that
"hub clients" are causing load issues on the servers, which is not
accurate ... most of our "big clients" are running on neptune, where no
postgresql.org VM is running, and the load on that machine *rarely* goes
above 5, and when it does, I just need to kill off one of the aspseek
processes and it drops back down again :)
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
