Re: Inefficient barriers on solaris with sun cc - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Inefficient barriers on solaris with sun cc
Date
Msg-id CA+TgmoaCKyME560vug7VthREe0a7pyczQuy4gjPS5p7czykoOw@mail.gmail.com
Whole thread Raw
In response to Inefficient barriers on solaris with sun cc  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Thu, Sep 25, 2014 at 9:34 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> Binaries compiled on solaris using sun studio cc currently don't have
> compiler and memory barriers implemented. That means we fall back to
> relatively slow generic implementations for those. Especially compiler,
> read, write barriers will be much slower than necessary (since they all
> just need to prevent compiler reordering as both sparc and x86 are run
> in TSO mode under solaris).
>
> Since my estimate is that we'll use more and more barriers, that's going
> to hurt more and more.
>
> I do *not* plan to do anything about it atm, I just thought it might be
> helpful to have this stated somewhere searchable.

To put that another way:

If there are any Sun Studio users out there who care about performance
on big iron, please send a patch to fix this...

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



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Next
From: Andres Freund
Date:
Subject: Re: Scaling shared buffer eviction