From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Erik Jones <ejones(at)engineyard(dot)com> |
Cc: | Gerd König <koenig(at)transporeon(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: high load on server |
Date: | 2009-04-04 11:16:39 |
Message-ID: | dcc563d10904040416n38b65529u104518b37746ac4c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Apr 3, 2009 at 4:13 PM, Erik Jones <ejones(at)engineyard(dot)com> wrote:
> Eh? His run queue constantly has procs waiting for run time, although I've
> seen higher. That with a distinct lack of heavy IO says cpu bound to me...
I just pulled up the linux man page and it says that r is the number
of processes waiting to run. This isn't entirely correct. A BSD or
Solaris man page more correctly identifies it as the number of
processes running OR waiting to run and that if this number exceeds
the number of cores then the number by which is exceeds it is how big
of a queue there is.
From | Date | Subject | |
---|---|---|---|
Next Message | Giorgio Valoti | 2009-04-04 12:19:50 | Re: Rule or Function and Trigger? |
Previous Message | c k | 2009-04-04 09:29:03 | strange behavior of plpgsql function |