Re: Possible performance regression in version 10.1 with pgbenchread-write tests. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Possible performance regression in version 10.1 with pgbenchread-write tests.
Date
Msg-id CA+TgmoZYLrs3zV44R1gEYaJ2dAGvmYKMA_k5R5vrx0tW=t29BA@mail.gmail.com
Whole thread Raw
In response to Possible performance regression in version 10.1 with pgbenchread-write tests.  (Mithun Cy <mithun.cy@enterprisedb.com>)
Responses Re: Possible performance regression in version 10.1 with pgbenchread-write tests.
List pgsql-hackers
On Wed, Feb 21, 2018 at 10:03 PM, Mithun Cy <mithun.cy@enterprisedb.com> wrote:
> seeing futex in the call stack andres suggested that following commit could
> be the reason for regression
>
> commit ecb0d20a9d2e09b7112d3b192047f711f9ff7e59
> Author: Tom Lane <tgl@sss.pgh.pa.us>
> Date:   2016-10-09 18:03:45 -0400
>
>     Use unnamed POSIX semaphores, if available, on Linux and FreeBSD.
>
> Commenting out same in src/template/linux I did run the benchmark tests
> again
> performance improved from 26871.567326 to 34286.620251 (both median of 3
> TPS).

Hmm.  So that commit might not have been the greatest idea.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Charge cpu_tuple_cost * 0.5 for Append and MergeAppend nodes.
Next
From: Robert Haas
Date:
Subject: Re: [doc fix] Correct calculation of vm.nr_hugepages