| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ants Aasma <ants(at)cybertec(dot)at>, 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-22 19:05:56 |
| Message-ID: | CAHyXU0xMFvr2eiR+2Lv=dj+UON+muei_pjbUP2BMetiR-UTASw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 22, 2013 at 1:13 PM, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> wrote:
> On Fri, Mar 22, 2013 at 11:36 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
>> On Fri, Mar 22, 2013 at 2:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> And we definitely looked at ARC
>>
>> We didn't just look at it. At least one release used it. Then patent
>> issues were raised (and I think the implementation had some contention
>> problems).
>>
>>
>> --
>> greg
>
> What is the general thinking? Is it time to start testing again and
> thinking about improvements to the current algorithm?
well, what problem are you trying to solve exactly? the main problems
I see today are not so much in terms of page replacement but spinlock
and lwlock contention.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2013-03-22 19:06:52 | Re: Default connection parameters for postgres_fdw and dblink |
| Previous Message | Tom Lane | 2013-03-22 18:49:15 | Re: dump, restore, dump yields differences |