Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 22A0E1337B5C for ; Mon, 20 Dec 2010 11:41:00 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 30980-04 for ; Mon, 20 Dec 2010 15:40:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from eagle.jhcloos.com (eagle.jhcloos.com [207.210.242.212]) by mail.postgresql.org (Postfix) with ESMTP id 584881337B58 for ; Mon, 20 Dec 2010 11:40:52 -0400 (AST) Received: by eagle.jhcloos.com (Postfix, from userid 10) id B9E784025D; Mon, 20 Dec 2010 15:40:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhcloos.com; s=eagle; t=1292859651; bh=nxfdPFR4fi54g+26GhD2rxIoVz+I6igQIx18Qn+FpzQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=C5pF5iFuN3xinnHwsqGAUKyBe+5Ps24MmHQBWGUMh9gfOTh0k0OYy/+uS8dTnLXgZ i6jlLW/Lht3fOz18sn3fMtkDXVJVFKZYOrp2hLazx7JL6vjL89vrIjzqEPAWPDeJ/P wBtL14irE2J4Qjx1nfOTIeGnbn2JoOs+tu6YE9s0= Received: from carbon (localhost [127.0.0.1]) by carbon.jhcloos.org (Postfix) with ESMTP id E853430002A; Mon, 20 Dec 2010 15:33:26 +0000 (UTC) From: James Cloos To: Mladen Gogala Cc: Royce Ausburn , "pgsql-performance\@postgresql.org" Subject: Re: CPU bound In-Reply-To: <4D0EFC02.7040004@vmsinfo.com> (Mladen Gogala's message of "Mon, 20 Dec 2010 01:47:30 -0500") References: <4D0EFC02.7040004@vmsinfo.com> User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAI1J REFUOE+lU9ESgCAIg64P1y+ngUdxhl5H8wFbbM0OmUiEhKkCYaZThXCo6KE5sCbA1DDX3genvO4d eBQgEMaM5qy6uWk4SfBYfdu9jvBN9nSVDOKRtwb+I3epboOsOX5pZbJNsBJFvmQQ05YMfieIBnYX FK2N6dOawd97r/e8RjkTLzmMsiVgrAoEugtviCM3v2WzjgAAAABJRU5ErkJggg== Copyright: Copyright 2009 James Cloos OpenPGP: ED7DAEA6; url=http://jhcloos.com/public_key/0xED7DAEA6.asc OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 Date: Mon, 20 Dec 2010 10:33:26 -0500 Message-ID: Lines: 14 MIME-Version: 1.0 Content-Type: text/plain X-Hashcash: 1:30:101220:mladen.gogala@vmsinfo.com::pCJcnfPJFv6V3LYG:00000000000000000000000000000000000RBO2K X-Hashcash: 1:30:101220:royce@inomial.com::BZ7gm2oIyKbGvZ5Q:0000000000000000000000000000000000000000000XHZU/ X-Hashcash: 1:30:101220:"pgsql-performance\@postgresql.org"::Hkm4qC4z+kVMDn8M:0000000000000000000000000JaCNa X-Hashcash: 1:30:101220:pgsql-performance@postgresql.org::9NlWcZgFDaIfj20Y:0000000000000000000000000000Mw4+S X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/252 X-Sequence-Number: 41704 >>>>> "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? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6