On Tue, May 3, 2016 at 11:22 AM, Andres Freund <and...@anarazel.de> wrote:
> The issue with 0 v. -1 (and 0 vs. > 0 makes a big performance > difference, so it's not that surprising to interpret numbers that way) ... if you fail to read the documentation of the feature or the code implementing it before testing. > was immediately addressed by another round of benchmarks after you > pointed it out. Which showed a 4% maximum hit before moving the test for whether it was "off" inline. (I'm not clear from the posted results whether that was before or after skipping the spinlock when the feature was off.) All tests that I have done and that others have done (some on big NUMA machines) and shared with me show no regression now. I haven't been willing to declare victory on that basis without hearing back from others who were able to show a regression before. If there is still a regression found when "off", there is one more test of old_snapshot_threshold which could easily be shifted in-line; it just seems unnecessary given the other work done in that area unless there is evidence that it is really needed. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
