Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 3A5D79FB62C for ; Sun, 20 May 2007 17:42:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 55586-02 for ; Sun, 20 May 2007 17:41:55 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from telogis.co.nz (telogis.co.nz [203.98.10.169]) by postgresql.org (Postfix) with ESMTP id 94BEC9FB33C for ; Sun, 20 May 2007 17:41:58 -0300 (ADT) Received: from RALPH2 ([::ffff:192.168.3.157]) by telogis.co.nz with esmtp; Mon, 21 May 2007 08:41:57 +1200 id 00978C2A.4650B295.00002FCB From: "Ralph Mason" To: "'Mark Lewis'" Cc: pgsql-performance@postgresql.org References: <011b01c798d5$141365a0$3c3a30e0$@mason@telogis.com> <1179496683.31471.72.camel@archimedes> In-Reply-To: <1179496683.31471.72.camel@archimedes> Subject: Re: Ever Increasing IOWAIT Date: Mon, 21 May 2007 08:41:41 +1200 Message-ID: <005c01c79b1f$459c2160$d0d46420$@mason@telogis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AceZVNtdNIBT+Zh0TKmplZ8CDVR2SABykjSQ Content-Language: en-nz X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/385 X-Sequence-Number: 24775 >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 No - no swap on this machine. The number of connections is stable. Ralph 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. >=20 > =20 >=20 > The weird thing is that if we restart postgres it=E2=80=99s fine for = hours but > over time it goes bad again. >=20 > =20 >=20 > (CPU usage graph here > http://www.flickr.com/photos/8347741@N02/502596262/ ) You can clearly > see where the restart happens in the IO area >=20 > =20 >=20 > This is Postgres 8.1.4 64bit. >=20 > =20 >=20 > Anyone have any ideas? >=20 > =20 >=20 > Thanks >=20 > Ralph >=20 > =20 >=20 >=20 >=20 > -- > 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. >=20 >=20 ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate --=20 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. =20 --=20 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. =20