Re: [HACKERS] An attempt to reduce WALWriteLock contention

Поиск
Список
Период
Сортировка
От jasrajd
Тема Re: [HACKERS] An attempt to reduce WALWriteLock contention
Дата
Msg-id 1498031852888-5967786.post@n3.nabble.com
обсуждение исходный текст
Ответ на [HACKERS] An attempt to reduce WALWriteLock contention  (Kuntal Ghosh <kuntalghosh.2007@gmail.com>)
Ответы 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>)
Список 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 по дате отправления:

Предыдущее
От: Shubham Barai
Дата:
Сообщение: Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index
Следующее
От: Etsuro Fujita
Дата:
Сообщение: [HACKERS] Useless code in ExecInitModifyTable