X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D78389DC808 for ; Thu, 16 Mar 2006 06:45:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83421-01 for ; Thu, 16 Mar 2006 06:45:13 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by postgresql.org (Postfix) with ESMTP id 97C709DC849 for ; Thu, 16 Mar 2006 06:45:09 -0400 (AST) Received: by zproxy.gmail.com with SMTP id 8so311842nzo for ; Thu, 16 Mar 2006 02:45:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VPQXOYzqQvXr+hGuNDq4RtqwzZZni/m6TYQM/eohqH/WGnwdaxJfmrgbu/3agPYrvxX8x5ShCTXkJbJSIN3+fF3DElCorjAFpfqRNkpxIJZUNmVFneq4q5+/BgILfBYReugPlaH0MQJ5wuYQ/JA4t7PQzWBmf1N6ZeZNzjH/6LM= Received: by 10.65.158.13 with SMTP id k13mr621390qbo; Thu, 16 Mar 2006 02:45:12 -0800 (PST) Received: by 10.65.123.12 with HTTP; Thu, 16 Mar 2006 02:45:12 -0800 (PST) Message-ID: <1d4e0c10603160245n55128e86t35431a339afcf8cc@mail.gmail.com> Date: Thu, 16 Mar 2006 11:45:12 +0100 From: "Guillaume Smet" To: pgsql-performance@postgresql.org Subject: PostgreSQL and Xeon MP MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.302 required=5 tests=[AWL=0.302] X-Spam-Score: 0.302 X-Spam-Level: X-Archive-Number: 200603/230 X-Sequence-Number: 17667 Hello, We are experiencing performances problem with a quad Xeon MP and PostgreSQL 7.4 for a year now. Our context switch rate is not so high but the load of the server is blocked to 4 even on very high load and we have 60% cpu idle even in this case. Our database fits in RAM and we don't have any IO problem. I saw this post from Tom Lane http://archives.postgresql.org/pgsql-performance/2004-04/msg00249.php and several other references to problem with Xeon MP and I suspect our problems are related to this. We tried to put our production load on a dual standard Xeon on monday and it performs far better with the same configuration parameters. I know that work has been done by Tom for PostgreSQL 8.1 on multiprocessor support but I didn't find any information on if it solves the problem with Xeon MP or not. My question is should we expect a resolution of our problem by switching to 8.1 or will we still have problems and should we consider a hardware change? We will try to upgrade next tuesday so we will have the real answer soon but if anyone has any experience or information on this, he will be very welcome. Thanks for your help. -- Guillaume