From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Юрий Соколов <funny(dot)falcon(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Clock with Adaptive Replacement |
Date: | 2018-04-29 19:48:27 |
Message-ID: | 20180429194827.vtklyp76q7fkimgr@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018-04-25 11:31:12 +0500, Andrey Borodin wrote:
>
>
> > 24 апр. 2018 г., в 23:14, Andres Freund <andres(at)anarazel(dot)de> написал(а):
> >
> > On 2018-04-24 17:16:47 +0500, Andrey Borodin wrote:
> >> But, I think that cost of development of real page eviction strategy
> >> itself is neglectable small compared to infrastructure changes needed
> >> by any non-CS5 strategy.
> >
> > What problems are you seeing? This isn't a lot of code?
> 1. Teaching BgWriter to used data from eviction strategy to aggressively flush data to disk (instead of ++next_to_clean )
> 2. Implementing strategies as lock-free algorithms for freelist
> These parts seem most important for benchmarking.
> Also:
> 3. Converting all rings to single buffer manager where possible
> 4. Using O_DIRECT while writing data files
> 5. Using aio and scheduling of writes
> These parts are not necessary, but most challenging, while not impossible though.
These largely seem to be increasing the scope beyond reason...
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-04-29 21:19:00 | Re: power() function in Windows: "value out of range: underflow" |
Previous Message | Юрий Соколов | 2018-04-29 19:39:20 | Re: [HACKERS] Clock with Adaptive Replacement |