From: | Jean-Michel POURE <jmpoure(at)translationforge(dot)com> |
---|---|
To: | <valeria(at)saolucas-se(dot)com(dot)br> |
Cc: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: PERFORMANCE |
Date: | 2002-04-18 20:17:05 |
Message-ID: | 200204182217.06005.jmpoure@translationforge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
Le Jeudi 18 Avril 2002 21:54, valeria(at)saolucas-se(dot)com(dot)br a écrit :
> Top result when the server is almost stoping ...
>
> 4:19pm up 2 days, 3:04, 2 users, load average: 4.26, 4.06, 4.59
> 102 processes: 96 sleeping, 6 running, 0 zombie, 0 stopped
> CPU0 states: 83.0% user, 15.0% system, 0.0% nice, 0.1% idle
> CPU1 states: 82.0% user, 16.0% system, 0.0% nice, 0.1% idle
> Mem: 771384K av, 699676K used, 71708K free, 0K shrd, 6488K buff
> Swap: 522232K av, 77420K used, 444812K free
Load avarage is 4.26. A large query seems to overflow the system.
Type command "top" to make sure PostgreSQL is really at stake.
Then, modify /etc/init.d/postgresql to run PostgreSQL in debug mode:
postmaster ... -d debug-level
Restart PostgreSQL service entering:
"service postgresql restart"
This will log all queries and may help you understand what is going on.
Best regards,
Jean-Michel POURE
From | Date | Subject | |
---|---|---|---|
Next Message | Dave | 2002-04-19 14:01:14 | Security - local(TRUST) and php/perl access |
Previous Message | Alexander Pucher | 2002-04-18 09:36:00 | Re: php-postgresql-application |