On 2017-06-21 00:57:32 -0700, jasrajd wrote: > We are also seeing contention on the walwritelock and repeated writes to the > same offset if we move the flush outside the lock in the Azure environment. > pgbench doesn't scale beyond ~8 cores without saturating the IOPs or > bandwidth. Is there more work being done in this area?
I kind of doubt that scalability limit is directly related to this patch - I've seen postgres scale furhter without that lock becoming the prime issue. What exactly are you measuring / observing?