| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Subject: | Re: Avoid stack frame setup in performance critical routines using tail calls |
| Date: | 2021-07-20 06:53:39 |
| Message-ID: | CAApHDvpfr07JBykytxDXLxMjtExgmSKRUaR4dXkAt5xaGumUBA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 20 Jul 2021 at 18:17, Andres Freund <andres(at)anarazel(dot)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 | Content-Type | Size |
|---|---|---|
| AllocateSetAlloc.txt | text/plain | 6.1 KB |
| palloc.txt | text/plain | 1.5 KB |
| percent.txt | text/plain | 577 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-07-20 07:03:51 | Re: Avoid stack frame setup in performance critical routines using tail calls |
| Previous Message | Andres Freund | 2021-07-20 06:16:57 | Re: Avoid stack frame setup in performance critical routines using tail calls |