Hi Max,
To find out what is causing the big load you could also try to use 'ATOP'
which can be found at http://www.atcomputing.nl/atop. This tool shows more
(accurate) information than the regular TOP.
There are also some kernel patches available which, when applied to your
kernel, even show more
On Thu, 23 Aug 2007 12:24:32 +0400, Hannes Dorbath
<[EMAIL PROTECTED]> wrote:
On 23.08.2007 11:04, Max Zorloff wrote:
When one postgres process waits for lock to release does it use any cpu?
And also, when apache waits for query to finish, does it use cpu?
No, but are you sure what you see
On 23.08.2007 11:04, Max Zorloff wrote:
When one postgres process waits for lock to release does it use any cpu?
And also, when apache waits for query to finish, does it use cpu?
No, but are you sure what you see is not i/o wait? What values does top
display in the %wa columns in the CPU rows?
On Thu, 23 Aug 2007 08:29:03 +0400, Tom Lane <[EMAIL PROTECTED]> wrote:
"Max Zorloff" <[EMAIL PROTECTED]> writes:
... The problem is that after the number of concurrent users rises to
100, CPU becomes almost 100% loaded. How do I find out what's hogging
the
CPU?
'top' shows demon using 8%
Hi Max,
To find out what is causing the big load you could also try to use 'ATOP'
which can be found at http://www.atcomputing.nl/atop. This tool shows more
(accurate) information than the regular TOP.
There are also some kernel patches available which, when applied to your
kernel, even show more
"Max Zorloff" <[EMAIL PROTECTED]> writes:
> ... The problem is that after the number of concurrent users rises to
> 100, CPU becomes almost 100% loaded. How do I find out what's hogging the
> CPU?
> 'top' shows demon using 8% cpu on top, and some amount of postgres
> processes each using 2%
