| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, HeikkiLinnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Subject: | Re: profiling connection overhead |
| Date: | 2010-11-24 21:25:45 |
| Message-ID: | 21943.1290633945@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Nov 24, 2010, at 4:05 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Yes, but only once. Also scrubbing a page is faster than copying it... (and
>> there were patches floating around to do that in advance, not sure if they got
>> integrated into mainline linux)
> I'm not following - can you elaborate?
I think Andres is saying that bss space isn't optimized during a fork
operation: it'll be propagated to the child as copy-on-write pages.
Dunno if that's true or not, but if it is, it'd be a good reason to
avoid the scheme you're suggesting.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2010-11-24 21:28:43 | Re: profiling connection overhead |
| Previous Message | Andres Freund | 2010-11-24 21:19:09 | Re: profiling pgbench |