Re: Performance under contention - Mailing list pgsql-performance

From Robert Haas
Subject Re: Performance under contention
Date
Msg-id AANLkTin=vVgkpYe2u_WBVHV59dgbe5QZ6PZ-nsT28Yb5@mail.gmail.com
Whole thread Raw
In response to Re: Performance under contention  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Performance under contention
List pgsql-performance
2010/12/7 Robert Haas <robertmhaas@gmail.com>:
> 2010/12/7 Віталій Тимчишин <tivv00@gmail.com>:
>> As far as I can see from the source, there is a lot of code executed under
>> the partition lock protection, like two hash searches (and possibly
>> allocations).
>
> Yeah, that was my concern, too, though Tom seems skeptical (perhaps
> rightly).  And I'm not really sure why the PROCLOCKs need to be in a
> hash table anyway - if we know the PROC and LOCK we can surely look up
> the PROCLOCK pretty expensively by following the PROC SHM_QUEUE.

Err, pretty INexpensively.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: Performance under contention
Next
From: Vlad Arkhipov
Date:
Subject: Re: Slow BLOBs restoring