From: James Cloos <cloos@jhcloos.com>
To: 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 10:33:26 -0500
Message-ID: <m362uo5uht.fsf@jhcloos.com> (raw)
In-Reply-To: <4D0EFC02.7040004@vmsinfo.com>
References: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com>
<m38vzl6z17.fsf@jhcloos.com>
<4D0EFC02.7040004@vmsinfo.com>
>>>>> "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?
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
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: cloos@jhcloos.com, mladen.gogala@vmsinfo.com, royce@inomial.com
Subject: Re: CPU bound
In-Reply-To: <m362uo5uht.fsf@jhcloos.com>
* 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