| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Sokolov Yura <funny(dot)falcon(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fix performance of generic atomics |
| Date: | 2017-09-06 12:34:46 |
| Message-ID: | CANP8+jLAvKiQFP84OXM3kuMkipj9Tqn6aEO0163WjP1fGfTneQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 September 2017 at 21:23, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
>> What scale factor and client count? How many cores per socket? It looks
>> like Sokolov was just starting to see gains at 200 clients on 72 cores,
>> using -N transaction.
...
> Moreover, it matters which primitive you're testing, on which platform,
> with which compiler, because we have a couple of layers of atomic ops
> implementations.
...
I think Sokolov was aiming at 4-socket servers specifically, rather
than as a general performance gain.
If there is no gain on 2-socket, at least there is no loss either.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-09-06 12:42:05 | Re: <> join selectivity estimate question |
| Previous Message | Tom Lane | 2017-09-06 12:25:56 | Re: document and use SPI_result_code_string() |