Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 285D92E0044 for ; Wed, 23 Apr 2008 08:19:32 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 85182-04 for ; Wed, 23 Apr 2008 08:19:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by developer.postgresql.org (Postfix) with ESMTP id C73132E0083 for ; Wed, 23 Apr 2008 08:19:27 -0300 (ADT) Received: from mailsrv.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id C8F41BE0 for ; Wed, 23 Apr 2008 13:19:47 +0200 (CEST) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id 2AE07BFD7 for ; Wed, 23 Apr 2008 13:19:21 +0200 (CEST) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: confused of buffers and memory settings Date: Wed, 23 Apr 2008 13:19:23 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <480F0C92.8050907@transporeon.com> In-Reply-To: <480F0C92.8050907@transporeon.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8976748.1uacCiSEDj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200804231319.24090@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.013 tagged_above=0 required=5 tests=AWL=0.013 X-Spam-Level: X-Archive-Number: 200804/234 X-Sequence-Number: 28998 --nextPart8976748.1uacCiSEDj Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mittwoch, 23. April 2008 Gerd K=F6nig wrote: > The db will be accessed heavily (~20 requests/sec.)=20 > with a read/write ration of 50:50, yes, a lot of write activity. Not really heavy, I would say, but maybe your transactions are very big=20 and produce a lot of I/O. > I thought of setting "shared_buffers" to 750000 (~6GB) but how > depends this on the kernel buffer setting in /etc/sysctl.conf (what > is the interaction between these two settings?). > I know the variable "shmmax" can be defined, but currently there's no > such entry. # Shared Mem Maximum example: kernel.shmmax =3D 950123456 # do not allow memory overcommit to prevent database crashes vm.overcommit_memory=3D2 > The meaning of "work_mem" / "maintenance_work_mem" and "wal_buffers" > is also not clear. The maintenance_work_mem influences the size of > the WAL logs..?!? > What else are "top performance related" options for the usage > scenario I described earlier ? http://www.postgresql.org/docs/8.3/interactive/runtime-config-resource.html mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart8976748.1uacCiSEDj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBIDxs8zhSR9xwSCbQRAvRhAJ9u8ZrEgqimg1Br4LFWq9AoxxTw3ACg90S+ c2FkKu5kNQdhAXvq34C9Wuc= =Qwtm -----END PGP SIGNATURE----- --nextPart8976748.1uacCiSEDj--