On Mon, Sep 14, 2015 at 9:06 PM, Andres Freund <and...@anarazel.de> wrote: > On 2015-09-14 17:41:42 +0200, Andres Freund wrote: >> I pointed out how you can actually make this safely lock-free giving you >> the interesting code. > > And here's an actual implementation of that approach. It's definitely > work-in-progress and could easily be optimized further. Don't have any > big machines to play around with right now tho.
Are you confident this is faster across all workloads? Pin/Unpin are probably faster but this comes at a cost of extra atomic ops during the clock sweep loop. I wonder if this will degrade results under heavy contention. Also, I'm curious about your introduction of __builtin_expect() macros. Did you measure any gain from them? I bet there are other places they could be used -- for example the mvcc hint bit checks on xmin. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
