X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id DD77ED1C4E3 for ; Mon, 28 Jul 2003 16:26:19 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 00247-10 for ; Mon, 28 Jul 2003 13:25:22 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id D7DE9D1C4C9 for ; Mon, 28 Jul 2003 13:26:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h6SGPvQ3010186; Mon, 28 Jul 2003 12:25:58 -0400 (EDT) To: Franco Bruno Borghesi Cc: Josh Berkus , Daniel Migowski , pgsql-performance@postgresql.org Subject: Re: Mapping a database completly into Memory In-reply-to: <1059401815.749.7.camel@taz.oficina> References: <97842368.20030727104901@artis.uni-oldenburg.de> <9002.1059322732@sss.pgh.pa.us> <200307272114.11579.josh@agliodbs.com> <1059401815.749.7.camel@taz.oficina> Comments: In-reply-to Franco Bruno Borghesi message dated "28 Jul 2003 11:16:55 -0300" Date: Mon, 28 Jul 2003 12:25:57 -0400 Message-ID: <10185.1059409557@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/439 X-Sequence-Number: 2732 Franco Bruno Borghesi writes: > wouldn't also increasing shared_buffers to 64 or 128 MB be a good > performance improvement? This way, pages belonging to heavily used > indexes would be already cached by the database itself. Not necessarily. The trouble with large shared_buffers settings is you end up with lots of pages being doubly cached (both in PG's buffers and in the kernel's disk cache), thus wasting RAM. If we had a portable way of preventing the kernel from caching the same page, it would make more sense to run with large shared_buffers. regards, tom lane