From: Mladen Gogala <mladen.gogala@vmsinfo.com>
To: Jim Nasby <Jim@Nasby.net>
Cc: James Cloos <cloos@jhcloos.com>
Cc: Royce Ausburn <royce@inomial.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: CPU bound
Date: Mon, 03 Jan 2011 11:17:18 -0500
Message-ID: <4D21F68E.9070004@vmsinfo.com> (raw)
In-Reply-To: <5509F55C-FA66-4813-89C3-B2E62F6E8F49@Nasby.net>
References: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com>
<m38vzl6z17.fsf@jhcloos.com>
<4D0EFC02.7040004@vmsinfo.com>
<5509F55C-FA66-4813-89C3-B2E62F6E8F49@Nasby.net>
Jim Nasby wrote:
> On Dec 20, 2010, at 12:47 AM, Mladen Gogala wrote:
>
>> Good time accounting is the most compelling reason for having a wait event interface, like Oracle. Without the wait event interface, one cannot really tell where the time is spent, at least not without profiling the database code, which is not an option for a production database.
>>
>
> Out of curiosity, have you tried using the information that Postgres exposes to dtrace? I suspect it comes close to what you can get directly out of Oracle...
> --
> Jim C. Nasby, Database Architect jim@nasby.net
> 512.569.9461 (cell) http://jim.nasby.net
>
>
>
>
No, I haven't but I looked it in the documentation. I surmise, however,
that I will have to build my software with "--enable-dtrace", which is
not enabled by default. This certainly looks promising.
--
Mladen Gogala
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251
http://www.vmsinfo.com
The Leader in Integrated Media Intelligence Solutions
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: mladen.gogala@vmsinfo.com, Jim@Nasby.net, cloos@jhcloos.com, royce@inomial.com
Subject: Re: CPU bound
In-Reply-To: <4D21F68E.9070004@vmsinfo.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