Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 028781337BCC for ; Mon, 20 Dec 2010 11:49:02 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 30049-03-4 for ; Mon, 20 Dec 2010 15:48:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mh4.mail.rice.edu (mh4.mail.rice.edu [128.42.199.11]) by mail.postgresql.org (Postfix) with ESMTP id EC1F21337BC9 for ; Mon, 20 Dec 2010 11:48:48 -0400 (AST) Received: from mh4.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh4.mail.rice.edu (Postfix) with ESMTP id 719D928F8D7; Mon, 20 Dec 2010 09:48:48 -0600 (CST) X-Virus-Scanned: by amavis-2.6.4 at mh4.mail.rice.edu, auth channel Received: from mh4.mail.rice.edu ([127.0.0.1]) by mh4.mail.rice.edu (mh4.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id oOIz8HxAXS+W; Mon, 20 Dec 2010 09:48:48 -0600 (CST) X-SMTP-Auth: no X-SMTP-Auth: no X-SMTP-Auth: no X-SMTP-Auth: no Received: from aart.is.rice.edu (aart.is.rice.edu [168.7.56.48]) by mh4.mail.rice.edu (Postfix) with ESMTP id 4418228F88F; Mon, 20 Dec 2010 09:48:48 -0600 (CST) Received: by aart.is.rice.edu (Postfix, from userid 18612) id CEE1D2D5A6; Mon, 20 Dec 2010 09:48:47 -0600 (CST) Date: Mon, 20 Dec 2010 09:48:47 -0600 From: Kenneth Marshall To: James Cloos Cc: Mladen Gogala , Royce Ausburn , "pgsql-performance@postgresql.org" Subject: Re: CPU bound Message-ID: <20101220154847.GX10252@aart.is.rice.edu> References: <4D0EFC02.7040004@vmsinfo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/253 X-Sequence-Number: 41705 On Mon, Dec 20, 2010 at 10:33:26AM -0500, James Cloos wrote: > >>>>> "MG" == Mladen Gogala writes: > > MG> Good time accounting is the most compelling reason for having a wait > MG> event interface, like Oracle. Without the wait event interface, one > MG> cannot really tell where the time is spent, at least not without > MG> profiling the database code, which is not an option for a production > MG> database. > > And how exactly, given that the kernel does not know whether the CPU is > active or waiting on ram, could an application do so? > Exactly. I have only seen this data from hardware emulators. It would be nice to have... :) Ken