Re: [HACKERS] Clock with Adaptive Replacement - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Clock with Adaptive Replacement
Date
Msg-id 20180429194827.vtklyp76q7fkimgr@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Clock with Adaptive Replacement  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: [HACKERS] Clock with Adaptive Replacement  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
On 2018-04-25 11:31:12 +0500, Andrey Borodin wrote:
> 
> 
> > 24 апр. 2018 г., в 23:14, Andres Freund <andres@anarazel.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


pgsql-hackers by date:

Previous
From: Юрий Соколов
Date:
Subject: Re: [HACKERS] Clock with Adaptive Replacement
Next
From: Tom Lane
Date:
Subject: Re: power() function in Windows: "value out of range: underflow"