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 A3361D1B561 for ; Wed, 22 Oct 2003 18:00:40 +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 58483-03 for ; Wed, 22 Oct 2003 15:00:10 -0300 (ADT) Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231]) by svr1.postgresql.org (Postfix) with SMTP id 300EFD1B55E for ; Wed, 22 Oct 2003 15:00:07 -0300 (ADT) Message-ID: <20031022175808.20661.qmail@web12608.mail.yahoo.com> Received: from [207.235.65.10] by web12608.mail.yahoo.com via HTTP; Wed, 22 Oct 2003 10:58:08 PDT Date: Wed, 22 Oct 2003 10:58:08 -0700 (PDT) From: Simon Sadedin Subject: Re: poor cpu utilization on dual cpu box To: Josh Berkus , pgsql-performance@postgresql.org In-Reply-To: <200310220911.14853.josh@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/582 X-Sequence-Number: 4330 The suggestion that we are saturating the memory bus makes a lot of sense. We originally started with a low setting for shared buffers and resized it to fit all our tables (since we have memory to burn). That improved stand alone performance but not concurrent performance - this would explain that phenomenon somewhat. Will investigate further down this track. Thanks to everyone who responded! Cheers, Simon. Josh Berkus wrote:Simon, > The issue is that no matter how much query load we throw at our server it > seems almost impossible to get it to utilize more than 50% cpu on a > dual-cpu box. For a single connection we can use all of one CPU, but > multiple connections fail to increase the overall utilization (although > they do cause it to spread across CPUs). This is perfectly normal. It's a rare x86 machine (read fiber channel) where you don't saturate the I/O or the RAM *long* before you saturate the CPU. Transactional databases are an I/O intensive operation, not a CPU-intensive one. > We are running with shared buffers large enough to hold the > entire database Which is bad. This is not what shared buffers are for. See: http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html -- Josh Berkus Aglio Database Solutions San Francisco ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com