From: Kenneth Marshall <ktm@rice.edu>
To: James Cloos <cloos@jhcloos.com>
Cc: Mladen Gogala <mladen.gogala@vmsinfo.com>
Cc: Royce Ausburn <royce@inomial.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: CPU bound
Date: Mon, 20 Dec 2010 09:48:47 -0600
Message-ID: <20101220154847.GX10252@aart.is.rice.edu> (raw)
In-Reply-To: <m362uo5uht.fsf@jhcloos.com>
References: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com>
<m38vzl6z17.fsf@jhcloos.com>
<4D0EFC02.7040004@vmsinfo.com>
<m362uo5uht.fsf@jhcloos.com>
On Mon, Dec 20, 2010 at 10:33:26AM -0500, James Cloos wrote:
> >>>>> "MG" == Mladen Gogala <mladen.gogala@vmsinfo.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ktm@rice.edu, cloos@jhcloos.com, mladen.gogala@vmsinfo.com, royce@inomial.com
Subject: Re: CPU bound
In-Reply-To: <20101220154847.GX10252@aart.is.rice.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox