X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 2611B30DBF8 for ; Tue, 10 Jun 2003 15:48:27 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 04345-04 for ; Tue, 10 Jun 2003 12:48:16 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by svr1.postgresql.org (Postfix) with ESMTP id 3BAD030DBDB for ; Tue, 10 Jun 2003 12:48:16 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3108070; Tue, 10 Jun 2003 08:48:21 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Howard Oblowitz , pgsql-performance@postgresql.org Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning Date: Tue, 10 Jun 2003 08:46:21 -0700 User-Agent: KMail/1.4.3 Cc: rune.lending@inpoc.com References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200306100846.21875.josh@agliodbs.com> X-Archive-Number: 200306/30 X-Sequence-Number: 2114 Rune, > > shared_buffers = 117248 (shmmax / 2 / 1024 / 8 ) This I got from this > > forum. > > Does this sound right or am I totally out of bounds here? I have, as said Out of bounds, through no fault of your own .... I'm still working on documentation for this. However, let me qoute the upcoming supplimentary docs: SHARED_BUFFERS Sets the size of Postgres' memory buffer where queries are held before being fed into the Kernel buffer of the host system. It's very important to remember that this is only a holding area, and not the total memory available for the server. As such, resist the urge to set this number to a large portion of your RAM, as this will actually degrade performance on many OSes. Members of the pgsql-performance mailing list have found useful values in the range of 1000-6000, depending on available RAM, database size, and number of concurrent queries. No one has yet reported positive results for any number over 6000. -- Josh Berkus Aglio Database Solutions San Francisco