| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Memory Accounting v11 |
| Date: | 2015-07-07 09:43:54 |
| Message-ID: | 20150707094354.GE30359@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-07-07 16:49:58 +1200, David Rowley wrote:
> I've been looking at this patch and trying to reproduce the reported
> slowdown by using Tomas' function to try to exercise palloc() with minimal
> overhead of other code:
>
> https://github.com/tvondra/palloc_bench
That's not necessarily meaningful. Increased cache footprint (both data
and branch prediction) is often only noticeable with additional code
running pushing stuff out.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-07-07 09:46:17 | Re: Freeze avoidance of very large table. |
| Previous Message | Heikki Linnakangas | 2015-07-07 09:25:54 | Re: Transactions involving multiple postgres foreign servers |