On Thu, Mar 31, 2016 at 8:21 PM, Alexander Korotkov < a.korot...@postgrespro.ru> wrote:
> > I think these changes worth running benchmark again. I'm going to run it > on 4x18 Intel. > The results are following. clients master v3 v5 v9 1 11671 12507 12679 12408 2 24650 26005 25010 25495 4 49631 48863 49811 50150 8 96790 96441 99946 98383 10 121275 119928 124100 124180 20 243066 243365 246432 248723 30 359616 342241 357310 378881 40 431375 415310 441619 425653 50 489991 489896 500590 502549 60 538057 636473 554069 685010 70 588659 714426 738535 719383 80 405008 923039 902632 909126 90 295443 1181247 1155918 1179163 100 258695 1323125 1325019 1351578 110 238842 1393767 1410274 1421531 120 226018 1432504 1474982 1497122 130 215102 1465459 1503241 1521619 140 206415 1470454 1505380 1541816 150 197850 1475479 1519908 1515017 160 190935 1420915 1484868 1523150 170 185835 1438965 1453128 1499913 180 182519 1416252 1453098 1472945 It appears that atomic OR for LockBufHdr() gives small but measurable effect. Great idea, Andres! ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers