| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Van Fleet <vanfleet(at)us(dot)ibm(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: HACKERS[PROPOSAL] split ProcArrayLock into multiple parts |
| Date: | 2017-06-07 17:12:02 |
| Message-ID: | CA+TgmobZKpSHPs6Yr8-zvpxYdoLEPuKi2HNZJPL+5wHuCSNLZQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 7, 2017 at 12:29 PM, Jim Van Fleet <vanfleet(at)us(dot)ibm(dot)com> wrote:
>> The basic idea is clear from your description, but it will be better
>> if you share the patch as well. It will not only help people to
>> review and provide you feedback but also allow them to test and see if
>> they can reproduce the numbers you have mentioned in the mail.
>
> OK -- would love the feedback and any suggestions on how to mitigate the low
> end problems.
Did you intend to attach a patch?
> Sokolov Yura has a patch which, to me, looks good for pgbench rw
> performance. Does not do so well with hammerdb (about the same as base) on
> single socket and two socket.
Any idea why? I think we will have to understand *why* certain things
help in some situations and not others, not just *that* they do, in
order to come up with a good solution to this problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-06-07 17:17:31 | Re: Fix a typo in snapmgr.c |
| Previous Message | Robert Haas | 2017-06-07 17:08:39 | Re: Challenges preventing us moving to 64 bit transaction id (XID)? |