Re: Suspicious top output

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Rafael Barrera Oro <rafael(at)akyasociados(dot)com(dot)ar>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Suspicious top output
Date: 2008-04-23 05:43:27
Message-ID: Pine.GSO.4.64.0804230138310.22837@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, 22 Apr 2008, Rafael Barrera Oro wrote:

> Hello, i have a postgresql server running and from time to time it gets
> painfully slow.

The usual information you should always include when posting messages here
is PostgreSQL and operating system versions.

> When this happens i usually connect to the server and run a "top"
> command

The other thing you should fire up in another window is "vmstat 1" to
figure out just what's going on in general. The great thing about those
is you can save them when you're done and easily analyze the results later
easily, which is trickier to do with top.

> 71872 pgsql 1 4 0 48552K 42836K sbwait 1:41 4.79%
> postgres

Some searching found this interesting suggestion from Darcy about things
stuck in sbwait:

http://unix.derkeiler.com/Mailing-Lists/FreeBSD/performance/2004-03/0015.html

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message sathiya psql 2008-04-23 07:19:37 SELECT 'DBD::Pg ping test'
Previous Message Greg Smith 2008-04-23 05:11:01 Re: Background writer underemphasized ...