Re: W-TinyLfu for cache eviction - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: W-TinyLfu for cache eviction
Date
Msg-id CAB=Je-HFfjTTBuGnQnjN9hMkJEKncTriqjOnXfe+ArisLj-OVQ@mail.gmail.com
Whole thread Raw
In response to Re: W-TinyLfu for cache eviction  (Ants Aasma <ants.aasma@eesti.ee>)
Responses Re: W-TinyLfu for cache eviction  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
> a global lock would be good enough for a proof of concept that only
evaluates cache hit ratios.

I think emulator can be used to check hit ratios. That way we can see
how different algorithms affect hit ratio.

Is there a set of traces of "buffer load events"? (I did some Google
searches like "postgresql buffer cache trace" with no luck)
Is there an option that enables tracing of each requested buffer Id?

Frankly speaking, I've no access to PG instances with lots of data
(i.e. >10GiB).

> Maybe.  Want to code it up?

That would be interesting, however: I'm not fluent at C. I've never
written multithreaded C code either. I understand what a cache line is
though.
Anyway, before hacking a prototype it makes sense to gather some traces.

Vladimir



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Function and view to retrieve WAL receiver status
Next
From: Craig Ringer
Date:
Subject: Re: Proposal: custom compression methods