X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EAE83D1B46C for ; Sat, 6 Dec 2003 17:47:15 +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 52940-04 for ; Sat, 6 Dec 2003 13:46:44 -0400 (AST) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by svr1.postgresql.org (Postfix) with ESMTP id 25689D1B445 for ; Sat, 6 Dec 2003 13:46:39 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-35.mail.demon.net with esmtp (Exim 3.35 #1) id 1ASgVp-0009La-0Z; Sat, 06 Dec 2003 17:46:38 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id B44BC1740C; Sat, 6 Dec 2003 17:46:36 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 239D517333; Sat, 6 Dec 2003 17:46:34 +0000 (GMT) From: Richard Huxton To: LIANHE SHAO , pgsql-performance Subject: Re: query using cpu nearly 100%, why? Date: Sat, 6 Dec 2003 17:46:32 +0000 User-Agent: KMail/1.5 References: <19be88196606.19660619be88@jhmimail.jhmi.edu> In-Reply-To: <19be88196606.19660619be88@jhmimail.jhmi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312061746.33037.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/141 X-Sequence-Number: 5001 On Friday 05 December 2003 21:03, LIANHE SHAO wrote: > Hello, > I use php as front-end to query our database. When I use System Monitor to > check the usage of cpu and memory, I noticed that the cpu very easily gets > up to 100%. Is that normal? if not, could someone points out possible > reason? The idea is that CPU should go to 100% when there's work to be done, and drop off when the system is idle. There's nothing to be gained with having the CPU at 50% and taking twice as long to perform a task. -- Richard Huxton Archonet Ltd