Re: [PATCH] dtrace probes for memory manager - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: [PATCH] dtrace probes for memory manager
Date
Msg-id 1258148498.1316.76.camel@localhost
Whole thread Raw
In response to Re: [PATCH] dtrace probes for memory manager  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [PATCH] dtrace probes for memory manager
List pgsql-hackers
Alvaro Herrera píše v pá 13. 11. 2009 v 18:34 -0300:
> Zdenek Kotala wrote:
> > Attached patch contains new dtrace probes for memory management. Main
> > purpose is to analyze memory footprint - for example how many memory
> > needs transaction, peak memory per context, when memory block is reused
> > or when it is allocate by malloc and so on.
> 
> Having had to instrument these to figure out some problems, I'd give
> this patch a +1.  However, the performance argument is compelling.  As a
> compromise, maybe we could have a #define that needs to be turned on at
> compile time to enable these probes; so a regular dtrace-enabled build
> would not have them, but if you really needed to analyze memory
> allocations, you could recompile to turn them on.

But point of dtrace probes is that they are here without
recompilation :(. Do we have any test which we could use for performance
penalty testing? I don't think that overhead is significant.
Zdenek




pgsql-hackers by date:

Previous
From: Dan Colish
Date:
Subject: Re: CTE containing ambiguous columns
Next
From: Emilio Platzer
Date:
Subject: I need to code a float with magnitude (ie unit of measure)