X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EB1BBD1B1BE for ; Mon, 28 Jun 2004 18:47:07 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 46937-07 for ; Mon, 28 Jun 2004 21:47:05 +0000 (GMT) Received: from mail.praemunio.com (mail.praemunio.com [66.179.47.216]) by svr1.postgresql.org (Postfix) with SMTP id 265AFD1B18A for ; Mon, 28 Jun 2004 18:47:00 -0300 (ADT) Received: from localhost (HELO mail.knobbe.us) by localhost with SMTP; 28 Jun 2004 16:46:59 -0500 Received: from localhost (HELO ??) by localhost with SMTP; 28 Jun 2004 16:46:58 -0500 Subject: Re: postgres 7.4 at 100% From: Frank Knobbe To: josh@agliodbs.com Cc: pgsql-performance@postgresql.org In-Reply-To: <200406281240.02954.josh@agliodbs.com> References: <40DE5C25.6070805@familyhealth.com.au> <1088397641.1105.10.camel@localhost> <200406281240.02954.josh@agliodbs.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-99TmdPzWsPKlJ1X4XhCX" Message-Id: <1088459215.551.18.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 28 Jun 2004 16:46:55 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/279 X-Sequence-Number: 7337 --=-99TmdPzWsPKlJ1X4XhCX Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-06-28 at 14:40, Josh Berkus wrote: > As one of the writers of that article, let me point out: >=20 > " -- Medium size data set and 256-512MB available RAM: 16-32MB (2048-4096= )=20 > -- Large dataset and lots of available RAM (1-4GB): 64-256MB (8192-32768)= " >=20 > While this is probably a little conservative, it's still way bigger than = 40. I agree that 40 is a bit weak :) Chris' system has only 512 MB of RAM though. I thought the quick response "..for any kind of production server, try 5000-10000..." -- without considering how much memory he has -- was a bit... uhm... eager. Besides, if the shared memory is used to queue client requests, shouldn't that memory be sized according to workload (i.e. amount of clients, transactions per second, etc) instead of just taking a percentage of the total amount of memory? If there only a few connections, why waste shared memory on that when the memory could be better used as file system cache to prevent PG from going to the disk so often?=20 I understand tuning PG is almost an art form, yet it should be based on actual usage patterns, not just by system dimensions, don't you agree? Regards, Frank --=-99TmdPzWsPKlJ1X4XhCX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA4JHPJjGc5ftAw8wRAiVmAKCNNXVuHGZRqKTBBuGboJekcXF+1QCfQHL2 diFMDEKJWZXA7hwtT+OcWsM= =EdpX -----END PGP SIGNATURE----- --=-99TmdPzWsPKlJ1X4XhCX--