| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(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 17:55:17 |
| Message-ID: | 1260554117.2642.37.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bernd Helmle píše v pá 11. 12. 2009 v 17:13 +0100:
>
> --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?
When probes are activated they have performance impact. It is normal.
Important is that you can use it when you need it on production system.
No recompilation, no extra binary, no downtime and it is safe.
Performance impact depends on Dscript
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-11 17:55:50 | Re: [PATCH] dtrace probes for memory manager |
| Previous Message | David P. Quigley | 2009-12-11 17:44:26 | Re: SE-PostgreSQL/Lite Review |