| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Юрий Соколов <funny(dot)falcon(at)gmail(dot)com> |
| 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 12:16:47 |
| Message-ID: | 2E09D995-9294-4A21-989B-34B75F66938E@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2018-04-24 13:52:33 | Re: Built-in connection pooling |
| Previous Message | Etsuro Fujita | 2018-04-24 11:19:45 | Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled. |