Re: [PATCH] dtrace probes for memory manager

Поиск
Список
Период
Сортировка
От Zdenek Kotala
Тема Re: [PATCH] dtrace probes for memory manager
Дата
Msg-id 1260554117.2642.37.camel@localhost
обсуждение исходный текст
Ответ на Re: [PATCH] dtrace probes for memory manager  (Bernd Helmle <mailings@oopsware.de>)
Ответы Re: [PATCH] dtrace probes for memory manager  (Robert Haas <robertmhaas@gmail.com>)
Список 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@commandprompt.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "David P. Quigley"
Дата:
Сообщение: Re: Adding support for SE-Linux security
Следующее
От: "David P. Quigley"
Дата:
Сообщение: Re: SE-PostgreSQL/Lite Review