On Tue, Aug 25, 2015 at 5:21 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Thu, Aug 20, 2015 at 3:49 PM, Andres Freund <andres@anarazel.de> wrote: > > How hard did you try checking whether this causes regressions? This > > increases the number of atomics in the commit path a fair bit. I doubt > > it's really bad, but it seems like a good idea to benchmark something > > like a single full-throttle writer and a large number of readers. > > One way to test this is run pgbench read load (with 100 client count) and > write load (tpc-b - with one client) simultaneously and check the results. > I have tried this and there is lot of variation(more than 50%) in tps in > different runs of write load, so not sure if this is the right way to > benchmark it. > > Another possible way is to hack pgbench code and make one thread run > write transaction and others run read transactions.
I have hacked pgbench to achieve single-writer-multi-reader test and below
