Re: spinlock->pthread_mutex : first results with Jeff's pgbench+plsql - Mailing list pgsql-hackers

From Robert Haas
Subject Re: spinlock->pthread_mutex : first results with Jeff's pgbench+plsql
Date
Msg-id CA+Tgmoa=gs_Dw9dfbPO8DP2kR3pTMN6UWeTWU4fRxvtZXsSJ8Q@mail.gmail.com
Whole thread Raw
In response to spinlock->pthread_mutex : first results with Jeff's pgbench+plsql  (Nils Goroll <slink@schokola.de>)
Responses Re: spinlock->pthread_mutex : first results with Jeff's pgbench+plsql  (Nils Goroll <slink@schokola.de>)
List pgsql-hackers
On Mon, Jul 2, 2012 at 11:26 AM, Nils Goroll <slink@schokola.de> wrote:
> Please note that this is with 3.1.7. I understand that many scalability
> improvements have been implemented in later versions and it would have to be
> expected that using less synchronization points will imply that spinlock
> overhead is less. In other words, the results _should_ look less drastic with
> later versions.

3.1.7?

A major scalability bottleneck caused by spinlock contention was fixed
in 9.2 - see commit b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4.  I'm not
sure that it's very meaningful to do performance testing on versions
that are known to be out of date.

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


pgsql-hackers by date:

Previous
From: Nils Goroll
Date:
Subject: spinlock->pthread_mutex : first results with Jeff's pgbench+plsql
Next
From: Nils Goroll
Date:
Subject: Re: spinlock->pthread_mutex : first results with Jeff's pgbench+plsql