From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Ivan Zolotukhin <ivan(dot)zolotukhin(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 8.3 on FreeBSD 6.3, sudden performance degradations |
Date: | 2008-09-09 08:31:18 |
Message-ID: | Pine.GSO.4.64.0809090417410.572@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 8 Sep 2008, Ivan Zolotukhin wrote:
> Yep, update_process_title = off if it is important.
Have you considered turning it on so you can see what processes are most
involved in the spike? Normally in your situation I'd try to capture what
the output from top was during the problem period and match that with what
the processes involved are doing at the time, and you'll need that to see
inside the PG processes. If the event is random then this data can be
hard to capture, you might have to write some scripts to save top output
in batch mode and the output from ps.
Did you confirm that the slow periods aren't checkpoint-related? I've
seen some wacky stuff on Linux before where the system percentage went up
dramatically because the background disk I/O process got hyperactive.
Again, the way you can usually figure that out is to look at what top is
showing during that period. I suspect you'll find some daemon going
crazy. The vmstat and iostat info you included are certainly strange but
I don't know enough about FreeBSD to know exactly what would cause that.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-09-09 08:37:09 | Re: Install Postgres on a SAN volume? |
Previous Message | Greg Smith | 2008-09-09 08:08:45 | Re: Install Postgres on a SAN volume? |