X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 7A8B0475CEE for ; Wed, 9 Apr 2003 23:46:06 -0400 (EDT) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 0716D474E42 for ; Wed, 9 Apr 2003 23:46:02 -0400 (EDT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2954227; Wed, 09 Apr 2003 20:46:00 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: "Matthew Nuzum" , "'Pgsql-Performance'" Subject: Re: Caching (was Re: choosing the right platform) Date: Wed, 9 Apr 2003 20:45:29 -0700 User-Agent: KMail/1.4.3 References: <000601c2fefe$d4b07e80$6900a8c0@mattspc> In-Reply-To: <000601c2fefe$d4b07e80$6900a8c0@mattspc> MIME-Version: 1.0 Message-Id: <200304092045.29503.josh@agliodbs.com> Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, hits=-32.4 required=5.0 tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/103 X-Sequence-Number: 1609 Matthew, > ** Postgres is multi-process, not multi-threaded (?) Correct. > ** It's better to not use huge amount of sort-mem but instead let the OS = do > the caching (?) That's "don't use a huge amount of *shared_buffers*". Sort_mem is a differ= ent=20 setting. However, I have never seen a database use more than 32mb sort mem= =20 in a single process, so I don't think the 2GB limit will hurt you much ... > ** My needs are really not going to be as big as I think they are if I > manage the application/environment correctly (?) Your needs *per process*. Also, PostgreSQL is not as much of a consumer o= f=20 RAM as it is a consumer of disk I/O. > * FreeBSD is going to provide a better file system than Linux (because > Linux only supports large files on journaling filesystems which impose > extra over head) (this gleaned from this conversation and previous threads > in archives)=20 No, the jury is still out on this one. ReiserFS is optimized for small=20 files, and I've done well with it although some posters report stability=20 problems, though all second-hand. We hope to test this sometime in the=20 upcoming months. --=20 Josh Berkus Aglio Database Solutions San Francisco