Postgres Pro
Downloads
Home   >   mailing lists

Re: Avoid stack frame setup in performance critical routines using tail calls - Mailing list pgsql-hackers

From David Rowley
Subject Re: Avoid stack frame setup in performance critical routines using tail calls
Date
Msg-id CAApHDvpfr07JBykytxDXLxMjtExgmSKRUaR4dXkAt5xaGumUBA@mail.gmail.com
Whole thread Raw
In response to Re: Avoid stack frame setup in performance critical routines using tail calls  (Andres Freund <andres@anarazel.de>)
Responses Re: Avoid stack frame setup in performance critical routines using tail calls  ("Andres Freund" <andres@anarazel.de>)
List pgsql-hackers
Tree view 
On Tue, 20 Jul 2021 at 18:17, Andres Freund <andres@anarazel.de> wrote:
> Any chance you could show a `perf annotate AllocSetAlloc` and `perf annotate
> palloc` from a patched run? And perhaps how high their percentages of the
> total work are. E.g. using something like
> perf report -g none|grep -E 'AllocSetAlloc|palloc|MemoryContextAlloc|pfree'

Sure. See attached.

David
Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Avoid stack frame setup in performance critical routines using tail calls
Next
From: "Andres Freund"
Date:
Subject: Re: Avoid stack frame setup in performance critical routines using tail calls