Re: Improving spin-lock implementation on ARM.

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-11-30 07:46:48
Message-ID: CAPpHfdtOHKWZC5U3J5tV-Gs6g7LFZuj1POiOhg8Csj818HQX2g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 30, 2020 at 9:20 AM Krunal Bauskar <krunalbauskar(at)gmail(dot)com> wrote:
> Some of us may be surprised by the fact that enabling lse is causing regression (1816 -> 892 or 714 -> 610) with HEAD itself.
> While lse is meant to improve the performance. This, unfortunately, is not always the case at-least based on my previous experience with LSE.too.

I doubt this is correct. As Tom shown upthread, Apple clang have LSE
enabled by default [1]. It might happen that --CFLAGS="-O2
-march=armv8-a+lse" disables some other optimizations, which are
enabled by default in Apple clang...

Links
1. https://www.postgresql.org/message-id/663376.1606432828%40sss.pgh.pa.us

------
Regards,
Alexander Korotkov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2020-11-30 07:51:15 Re: [patch] [doc] Minor variable related cleanup and rewording of plpgsql docs
Previous Message Yulin PEI 2020-11-30 07:27:28 [PATCH] BUG FIX: Core dump could happen when VACUUM FULL in standalone mode