| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Ants Aasma <ants(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Page replacement algorithm in buffer cache |
| Date: | 2013-03-24 07:29:04 |
| Message-ID: | CAOeZVie5uVMbQaybs1s8W4WVV4EFcWvzH=4DY3=C6cW9KZut=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> I'll have to take a look. Removing *all spinning* from from page
> allocation though feels like it might be worthwhile to test (got to
> give some bonus points for being a very local change and simple to
> implement). I wonder if with more shared buffers you tend to sweep
> more buffers per allocation. (IIRC Jeff J was skeptical of that).
Replacing the spinning with TAS for buffer header sounds like a good idea.
Regards,
Atri
--
Regards,
Atri
l'apprenant
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2013-03-24 07:43:25 | Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |
| Previous Message | Atri Sharma | 2013-03-24 07:20:02 | Re: Page replacement algorithm in buffer cache |