| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Krunal Bauskar <krunalbauskar(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improving spin-lock implementation on ARM. |
| Date: | 2020-12-01 16:07:02 |
| Message-ID: | CAPpHfdufBrVyENs-XPYBhk9ysWUJo8t2YnavQer5TJFG6UDafg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 1, 2020 at 6:19 PM Krunal Bauskar <krunalbauskar(at)gmail(dot)com> wrote:
> I would request you guys to re-think it from this perspective to help ensure that PGSQL can scale well on ARM.
> s_lock becomes a top-most function and LSE is not a universal solution but CAS surely helps ease the main bottleneck.
CAS patch isn't proven to be a universal solution as well. We have
tested the patch on just a few processors, and Tom has seen the
regression [1]. The benchmark used by Tom was artificial, but the
results may be relevant for some real-life workload.
I'm expressing just my personal opinion, other committers can have
different opinions. I don't particularly think this topic is
necessarily a non-starter. But I do think that given ambiguity we've
observed in the benchmark, much more research is needed to push this
topic forward.
Links.
1. https://www.postgresql.org/message-id/741389.1606530957%40sss.pgh.pa.us
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2020-12-01 16:13:53 | Re: Phrase search vs. multi-lexeme tokens |
| Previous Message | Chapman Flack | 2020-12-01 16:03:35 | Re: Confusing behavior of psql's \e |