| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Stephen Frost <sfrost(at)snowman(dot)net>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, 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-05-03 19:37:12 |
| Message-ID: | CA+TgmoaNY7B6q=n+q8R8SJEtwX7aOmET4QJE5ZGom7yfO4UNtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 2, 2018 at 3:06 PM, Vladimir Sitnikov
<sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
> Sample output can be seen here:
> https://github.com/vlsi/pgsqlstat/tree/pgsqlio#pgsqlio
Neat. Not sure what generated this trace, but note this part:
3271838881374 88205 0 0 1663 16385 16604 0
3271840973321 4368 0 0 1663 16385 16604 1
3271842680626 4502 0 0 1663 16385 16604 1
3271846077927 4173 0 0 1663 16385 16604 1
If we want to avoid artificial inflation of usage counts, that kind of
thing would be a good place to start -- obviously 4 consecutive
accesses to the same buffer by the same backend doesn't justify a
separate usage count bump each time.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-05-03 19:56:42 | Re: unused_oids script is broken with bsd sed |
| Previous Message | Tom Lane | 2018-05-03 19:37:09 | Re: unused_oids script is broken with bsd sed |