Re: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)
От | Andres Freund |
---|---|
Тема | Re: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4) |
Дата | |
Msg-id | 20130121171525.GA24628@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4) (Steve Singer <steve@ssinger.info>) |
Ответы |
Re: Re: [PATCH] unified frontend support for pg_malloc
et al and palloc/pfree mulation (was xlogreader-v4)
|
Список | pgsql-hackers |
On 2013-01-21 11:59:18 -0500, Steve Singer wrote: > On 13-01-21 02:28 AM, Andres Freund wrote: > > > >I haven't removed it from the patch afaik, so it would be great to get a > >profile here! Its "only" for xlogdump, but that tool helped me immensely > >and I don't want to maintain it independently... > > Here is the output from tprof > > Here is the baseline: Any chance to do the test ontop of HEAD? The elog stuff has gone in only afterwards and might actually effect this enough to be relevant. Otherwise I have to say I am a bit confused by the mighty difference in costs attributed to AllocSetAlloc given the amount of calls should be exactly the same and the number of "trampoline" function calls should also stay the same. Greetings, Andres Freund --Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: