Re: LWLock Queue Jumping

Поиск
Список
Период
Сортировка
Искать
От
Stefan Kaltenbrunner
Тема
Re: LWLock Queue Jumping
Дата
Msg-id
4A9A4AFF.8020605@kaltenbrunner.cc
Ответ на
Re: LWLock Queue Jumping (Heikki Linnakangas)
Список
Дерево обсуждения
LWLock Queue Jumping Simon Riggs <simon@2ndQuadrant.com>
Re: LWLock Queue Jumping Greg Stark <gsstark@mit.edu>
Re: LWLock Queue Jumping Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: LWLock Queue Jumping Simon Riggs <simon@2ndQuadrant.com>
Re: LWLock Queue Jumping Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Heikki Linnakangas wrote:
> Greg Stark wrote:
>> On Fri, Aug 28, 2009 at 8:07 PM, Simon Riggs wrote:
>>> WALInsertLock is heavily contended and likely always will be even if we
>>> apply some of the planned fixes.
>> I've lost any earlier messages, could you resend the raw data on which
>> this is based?
> 
> I don't have any pointers right now, but WALInsertLock does often show
> up as a bottleneck in write-intensive benchmarks.

yeah I recently ran accross that issue with testing concurrent COPY 
performance:

http://www.kaltenbrunner.cc/blog/index.php?/archives/27-Benchmarking-8.4-Chapter-2bulk-loading.html
discussed here:

http://archives.postgresql.org/pgsql-hackers/2009-06/msg01019.php


and (iirc) also here:

http://archives.postgresql.org/pgsql-hackers/2009-06/msg01133.php


however the general issue is easily visible in almost any write 
intensive concurrent workload on a fast IO subsystem(ie 
pgbench,sysbench,...).


Stefan

В списке pgsql-hackers по дате отправления
От: Heikki Linnakangas
Дата:
Сообщение: Re: LWLock Queue Jumping
От: Jan Otto
Дата:
FAQ