Re: [HACKERS] An attempt to reduce WALWriteLock contention - Mailing list pgsql-hackers

From jasrajd
Subject Re: [HACKERS] An attempt to reduce WALWriteLock contention
Date
Msg-id 1498031852888-5967786.post@n3.nabble.com
Whole thread Raw
In response to [HACKERS] An attempt to reduce WALWriteLock contention  (Kuntal Ghosh <kuntalghosh.2007@gmail.com>)
Responses Re: [HACKERS] An attempt to reduce WALWriteLock contention  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] An attempt to reduce WALWriteLock contention  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
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?



--
View this message in context:
http://www.postgresql-archive.org/An-attempt-to-reduce-WALWriteLock-contention-tp5935907p5967786.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.



pgsql-hackers by date:

Previous
From: Shubham Barai
Date:
Subject: Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index
Next
From: Etsuro Fujita
Date:
Subject: [HACKERS] Useless code in ExecInitModifyTable