X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2163FD1B508 for ; Tue, 21 Oct 2003 21:35:00 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 56359-06 for ; Tue, 21 Oct 2003 18:34:30 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 3F155D1B509 for ; Tue, 21 Oct 2003 18:34:28 -0300 (ADT) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3803239; Tue, 21 Oct 2003 14:35:09 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "scott.marlowe" , Andrew Sullivan Subject: Re: Tuning for mid-size server Date: Tue, 21 Oct 2003 14:32:16 -0700 User-Agent: KMail/1.4.3 Cc: References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200310211432.16551.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/562 X-Sequence-Number: 4310 Scott, > I think where it makes sense is when you have something like a report=20 > server where the result sets may be huge, but the parellel load is load,= =20 > i.e. 5 or 10 users tossing around 100 Meg or more at time. I've found that that question makes the difference between using 6% & 12% .= ..=20 particularly large data transformations ... but not higher than that. And= =20 I've had ample opportunity to test on 2 reporting servers. For one thing= ,=20 with very large reports one tends to have a lot of I/O binding, which is=20 handled by the kernel. --=20 -Josh Berkus Aglio Database Solutions San Francisco