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 8F049D1B8B3 for ; Thu, 28 Aug 2003 16:42:41 +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 49772-01 for ; Thu, 28 Aug 2003 13:42:11 -0300 (ADT) Received: from wight.ymogen.net (unknown [217.27.240.153]) by svr1.postgresql.org (Postfix) with SMTP id CF646D1B8AB for ; Thu, 28 Aug 2003 13:42:09 -0300 (ADT) Received: (qmail 27964 invoked from network); 28 Aug 2003 16:37:21 -0000 Received: from unknown (HELO solent) (213.165.136.12) by wight.ymogen.net with SMTP; 28 Aug 2003 16:37:21 -0000 From: "Matt Clark" To: "Rod Taylor" Cc: "Postgresql Performance" Subject: Re: Hardware recommendations to scale to silly load Date: Thu, 28 Aug 2003 17:37:24 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <1062081711.79027.55.camel@jester> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/422 X-Sequence-Number: 3238 > Ok.. I would be surprised if you needed much more actual CPU power. I > suspect they're mostly idle waiting on data -- especially with a Quad > Xeon (shared memory bus is it not?). In reality the CPUs get pegged: about 65% PG and 35% system. But I agree that memory throughput and latency is an issue. > Write performance won't matter very much. 3000 inserts/second isn't high > -- some additional battery backed write cache may be useful but not > overly important with enough ram to hold the complete dataset. I suspect > those are slow due to things like foreign keys -- which of course are > selects. 3000 inserts/sec isn't high when they're inside one transaction, but if each is inside its own transaction then that's 3000 commits/second. > case, additional ram will keep the system from hitting the disk for > writes as well. How does that work? > You may want to play around with checkpoints. Prevention of a checkpoint > during this hour will help prevent peaks. Be warned though, WAL will > grow very large, and recovery time should a crash occur could be > painful. Good point. I'll have a think about that.