On October 7, 2014 10:06:25 PM CEST, Kevin Grittner wrote:
>Robert Haas wrote:
>> On Tue, Oct 7, 2014 at 2:40 PM, Kevin Grittner
>wrote:
>>> Robert Haas wrote:
About a month ago, I told Kevin Grittner in an off-list
>conversation
that I'd work on providing him with some statistics abo
Robert Haas wrote:
> On Tue, Oct 7, 2014 at 2:40 PM, Kevin Grittner wrote:
>> Robert Haas wrote:
>>> About a month ago, I told Kevin Grittner in an off-list conversation
>>> that I'd work on providing him with some statistics about lwlock
>>> contention under SSI. I then ran a benchmark on a 16
On Tue, Oct 7, 2014 at 2:40 PM, Kevin Grittner wrote:
> Robert Haas wrote:
>> About a month ago, I told Kevin Grittner in an off-list conversation
>> that I'd work on providing him with some statistics about lwlock
>> contention under SSI. I then ran a benchmark on a 16-core,
>> 64-hardware thre
Robert Haas wrote:
> About a month ago, I told Kevin Grittner in an off-list conversation
> that I'd work on providing him with some statistics about lwlock
> contention under SSI. I then ran a benchmark on a 16-core,
> 64-hardware thread IBM server, testing read-only pgbench performance
> at sc
On Tue, Apr 09, 2013 at 07:49:51PM -0400, Robert Haas wrote:
> These locks are all SSI-related and they're all really hot. Lock 28
> is SerializableXactHashLock and lock 29 is
> SerializableFinishedListLock; both are acquired an order of magnitude
> more often than any non-SSI lock, and cause two
