Re: Skylake-S warning

One other thought.  Could we update pgxact->xmin less often?  What would be the impact of this lower bound being lower
thanit would normally be with the existing scheme.  Yes, it needs to be moved forward "occasionally".
 

FYI, be careful with padding PGXACT's to a full cache line.  With 1024 clients you'd completely blow out the L1 cache.
Thebenefits with less than 200 clients is dubious.  One problem with multiple(5) pgxact's in a single cache line is
thatyou may get a miss fetching xmin and then a second miss fetching xid because an invalidation occurs between the 2
fetchesfrom updating any of the other 5 pgxact's on the same cache line.  I've found some improvement fetching both
xminand xid with a single 64 bit fetch.  This prevents the invalidation between the two fetches.  Similarily updating
themwith a single 64 bit write helps.
 

Yes, this is uber tweaky.