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 C90DBD1C934 for ; Tue, 29 Jul 2003 15:22:52 +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 77941-03 for ; Tue, 29 Jul 2003 12:21:52 -0300 (ADT) Received: from lorax.kciLink.com (lorax.kciLink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id 16CE0D1C4B9 for ; Tue, 29 Jul 2003 12:22:51 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kciLink.com (Postfix) with ESMTP id A71D33E3B for ; Tue, 29 Jul 2003 11:22:50 -0400 (EDT) Received: from lorax.kciLink.com ([127.0.0.1]) by localhost (lorax.kciLink.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 37520-03 for ; Tue, 29 Jul 2003 11:22:40 -0400 (EDT) Received: by lorax.kciLink.com (Postfix, from userid 8) id 43D913E30; Tue, 29 Jul 2003 11:22:40 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: Mapping a database completly into Memory Date: Tue, 29 Jul 2003 11:22:40 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 21 Message-ID: References: <97842368.20030727104901@artis.uni-oldenburg.de> <9002.1059322732@sss.pgh.pa.us> <200307272114.11579.josh@agliodbs.com> <1059401815.749.7.camel@taz.oficina> <10185.1059409557@sss.pgh.pa.us> NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kciLink.com 1059492160 92135 216.194.193.105 (29 Jul 2003 15:22:40 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Tue, 29 Jul 2003 15:22:40 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, berkeley-unix) Cancel-Lock: sha1:08ptNhern9nM9vHhwXaK2wuEqZo= X-Virus-Scanned: by amavisd-new at kciLink.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/463 X-Sequence-Number: 2756 >>>>> "TL" == Tom Lane writes: TL> 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. TL> Not necessarily. The trouble with large shared_buffers settings is you TL> end up with lots of pages being doubly cached (both in PG's buffers and I think if you do a lot of inserting/updating to your table, then more SHM is better (and very high fsm settings), since you defer pushing out the dirty pages to the disk. For read-mostly, I agree that letting the OS do the caching is a better way. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/