Re: s_lock() seems too aggressive for machines with many sockets

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jan Wieck <jan(at)wi3ck(dot)info>, Nils Goroll <slink(at)schokola(dot)de>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: s_lock() seems too aggressive for machines with many sockets
Date: 2015-06-10 19:46:46
Message-ID: CA+TgmoYPS8KPxzYJ4zNFb8V8+b=-1KKS3Pt5bsAVHVarGJ4SUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 10, 2015 at 1:58 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Now that we (EnterpriseDB) have this 8-socket machine, maybe we could
>> try your patch there, bound to varying numbers of sockets.
>
> It'd be a significant amount of work to rebase it ontop current HEAD. I
> guess the easiest thing would be to try an older version of the patch
> with the xadd in place, and use a tree from back then.

We could do that, I guess. But we've made other significant
improvements in the meantime, so...

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-06-10 20:02:25 Re: Further issues with jsonb semantics, documentation
Previous Message Tom Lane 2015-06-10 19:35:10 Re: jsonb - path