> 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
