You're not swapping are you? One explanation could be that PG is
configured to think it has access to a little more memory than the box
can really provide, which forces it to swap once it's been running for
long enough to fill up its shared buffers or after a certain number of
concurrent connections are opened.
-- Mark Lewis
On Fri, 2007-05-18 at 10:45 +1200, Ralph Mason wrote:
> We have a database running on a 4 processor machine. As time goes by
> the IO gets worse and worse peeking at about 200% as the machine loads
> up.
>
>
>
> The weird thing is that if we restart postgres it’s fine for hours but
> over time it goes bad again.
>
>
>
> (CPU usage graph here
> http://www.flickr.com/photos/8347741@N02/502596262/ ) You can clearly
> see where the restart happens in the IO area
>
>
>
> This is Postgres 8.1.4 64bit.
>
>
>
> Anyone have any ideas?
>
>
>
> Thanks
>
> Ralph
>
>
>
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.15.9/573 - Release Date:
> 5/12/2006 4:07 p.m.
>
>
