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 BB43552C5C for ; Thu, 14 Jul 2005 00:17:42 -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 49237-03 for ; Thu, 14 Jul 2005 03:17:39 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 97FAD52824 for ; Thu, 14 Jul 2005 00:17:39 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j6E3HdaS050479 for ; Thu, 14 Jul 2005 03:17:39 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j6E3Do1x049325 for pgsql-performance@postgresql.org; Thu, 14 Jul 2005 03:13:50 GMT (envelope-from news) From: "Qingqing Zhou" X-Newsgroups: pgsql.performance Subject: Re: performance problems ... 100 cpu utilization Date: Thu, 14 Jul 2005 11:11:29 +0800 Organization: Hub.Org Networking Services Lines: 31 Message-ID: References: <42D567DB.6000100@works4me.com> Reply-To: "Qingqing Zhou" X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200507/158 X-Sequence-Number: 13399 "Dennis" writes > > checking the status of connections at this point ( ps -eaf | grep > "postgres:") where the CPU is maxed out I saw this: > > 127 idle > 12 bind > 38 parse > 34 select > Are you sure 100% CPU usage is solely contributed by Postgresql? Also, from the ps status you list, I can hardly see that's a problem because of problem you mentioned below. > > I know there has been discussion about problems on Xeon MP systems. Is > this what we are running into? Or is something else going on? Is there > other information I can provide that might help determine what is going on? > Here is a talk about Xeon-SMP spinlock contention problem: http://archives.postgresql.org/pgsql-performance/2005-05/msg00441.php Regards, Qingqing