Re: Avoid stack frame setup in performance critical routines using tail calls

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>

To: Andres Freund <andres@anarazel.de>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael.paquier@gmail.com>, Tomas Vondra <tv@fuzzy.cz>

Date: 2021-07-20T06:53:39Z

Lists: pgsql-hackers

Attachments

AllocateSetAlloc.txt (text/plain)
palloc.txt (text/plain)
percent.txt (text/plain)

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

Commits

Optimize GenerationAlloc() and SlabAlloc()
- a0cd95448067 17.0 landed
Refactor AllocSetAlloc(), separating hot and cold paths
- 413c18401dcc 17.0 landed
Adjust memory allocation functions to allow sibling calls
- 743112a2e993 17.0 landed