Re: [PATCH] dtrace probes for memory manager

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] dtrace probes for memory manager
Date: 2009-12-11 16:13:38
Message-ID: D6F60019FA32E1BEB3BA2614@[172.26.14.62]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On 11. Dezember 2009 11:28:54 -0300 Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:

>>
>> without compiled probes: AVG(2531.68)
>> with compiled probes: AVG(2511.97)
>
> Were the probes enabled?

Hmm, they were just compiled in, i didn't anything to instrument them with
dtrace.

I've just started a pgbench/dtrace run with instrumented probes aset_alloc,
aset_free and aset_realloc which just counts the calls to them during
pgbench, the first run gives me

tps = 1035.045523 (excluding connections establishing)

Ideas?

--
Thanks

Bernd

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2009-12-11 16:16:27 Re: Adding support for SE-Linux security
Previous Message KaiGai Kohei 2009-12-11 15:59:04 Re: Largeobject Access Controls (r2460)