On Wed, Jun 21, 2017 at 4:57 PM, jasrajd <jasr...@microsoft.com> 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?
As of now, there is no patch in the development queue for Postgres 11 that is dedicated to this particularly lock contention. There is a patch for LWlocks in general with power PC, but that's all: https://commitfest.postgresql.org/14/984/ Not sure if Kuntal has plans to submit again this patch. It is actually a bit sad to not see things moving on and use an approach to group flushes. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
