public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: [email protected]
Cc: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Simon Riggs <[email protected]>
Subject: Re: DTrace docs, Open Items and Performance
Date: Thu, 30 Nov 2006 19:30:31 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Tuesday 28 November 2006 10:05, Tom Lane wrote:
> Peter Eisentraut <[email protected]> writes:
> > Simon Riggs wrote:
> >> I'm planning to
> >> - add a new section to Performance Tips chapter called Dynamic
> >
> > In my mind it's a little late for revising the documentation structure.
> > I'd also think that DTrace is not a tuning tool but a monitoring tool
> > which might place it closer to the description of the statistics
> > collector.  I think the original plan even placed it into the Internals
> > part.
>
> I was about to say the same.  In my mind DTrace is primarily a hacker's
> tool --- I do not foresee the average DBA using it.  So it does not
> belong in the Performance Tips chapter.  A new chapter under Internals
> is probably as good as anything.
>

I'm not certain how best the postgresql specific probes will be used, but I 
might disagree with the above take as we're already using some kernel level 
dtrace probes to make DBA oriented tools...  see 
http://www.lethargy.org/~jesus/archives/74-PostgreSQL-performance-through-the-eyes-of-DTrace.html
for one specific example. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

view thread (5+ messages)

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: DTrace docs, Open Items and Performance
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox