From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Inefficient barriers on solaris with sun cc |
Date: | 2014-09-25 14:13:42 |
Message-ID: | CA+TgmoaCKyME560vug7VthREe0a7pyczQuy4gjPS5p7czykoOw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 25, 2014 at 9:34 AM, Andres Freund <andres(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-09-25 14:14:05 | Re: Scaling shared buffer eviction |
Previous Message | Simon Riggs | 2014-09-25 14:12:43 | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |