Re: [HACKERS] Clock with Adaptive Replacement

From: Юрий Соколов <funny(dot)falcon(at)gmail(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: 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-24 18:12:00
Message-ID: CAL-rCA2LuENMpS+FT7kucQ4+S3uHxV0R5sztDy1iTHucS+m2ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

вт, 24 апр. 2018 г., 15:16 Andrey Borodin <x4mmm(at)yandex-team(dot)ru>:

>
>
> > 24 апр. 2018 г., в 11:31, Юрий Соколов <funny(dot)falcon(at)gmail(dot)com>
> написал(а):
> >
> > Before implementing algorithms within PostgreSQL it will be great to
> test them outside with real traces.
> >
> > I think, there should be mechamism to collect traces from real-world
> postgresql instalations: every read and write access. It should be
> extremely eficient to be enabled in real world. Something like circular
> buffer in shared memory, and separate worker to dump it to disk.
> > Instead of full block address, 64bit hash could be used. Even 63bit +
> 1bit to designate read/write access.
> Yes, this is good idea to track pattern of blocks usage.
> 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.
>
> Best regards, Andrey Borodin.

Exactly. And it will be pity if implemented strategy will not be "the best".

Different strategies may need different infrastructure. And implementing
five infrastructures are certainly more expensive than choosing two best
strategies using traces and implementing them.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-04-24 18:14:49 Re: [HACKERS] Clock with Adaptive Replacement
Previous Message Andres Freund 2018-04-24 18:00:54 Fsync request queue