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
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
Ralph Mason [EMAIL PROTECTED] writes:
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
Ralph Mason [EMAIL PROTECTED] writes:
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
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
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
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 HYPERLINK
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
Hi Josh - thanks for thoughts.
This is Postgres 8.1.4 64bit.
1. Upgrade to 8.1.9. There is a bug with autovac that is fixed that is
pretty important.
We don't use pg_autovac - we have our own process that runs very often
vacuuming tables that are dirty. It works well and vacuums when
