Re: Improving spin-lock implementation on ARM. - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Improving spin-lock implementation on ARM.
Date
Msg-id CAPpHfdtaEco_Y2keGqWdxWX8pMe=9dxD30_9nBnH+9EOBYnVkw@mail.gmail.com
Whole thread Raw
In response to Improving spin-lock implementation on ARM.  (Krunal Bauskar <krunalbauskar@gmail.com>)
Responses Re: Improving spin-lock implementation on ARM.
List pgsql-hackers
On Tue, Dec 1, 2020 at 7:57 PM Zidenberg, Tsahi <tsahee@amazon.com> wrote:
> > On 01/12/2020, 16:59, "Alexander Korotkov" <aekorotkov@gmail.com> wrote:
> >  On Tue, Dec 1, 2020 at 1:10 PM Amit Khandekar <amitdkhan.pg@gmail.com> wrote:
> >   > FWIW, here is an earlier discussion on the same (also added the
> >    > proposal author here) :
>
> Thanks for looping me in!
>
> >    >
> >    > https://www.postgresql.org/message-id/flat/099F69EE-51D3-4214-934A-1F28C0A1A7A7%40amazon.com
> >
> >
> >    Thank you for pointing! I wonder why the effect of LSE on Graviton2
> >    observed by Tsahi Zidenberg is so modest.  It's probably because he
> >    runs the tests with a low number of clients.
>
> There are multiple possible reasons why I saw a smaller effect of LSE, but I think an important one was that I
> used a 32-core instance rather than a 64-core one. The reason I did so, was that 32-cores gave me better
> absolute results than 64 cores, and I didn't want to feel like I could misguide anyone.

BTW, what number of clients did you use?  I can't find it in your message.

------
Regards,
Alexander Korotkov



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improving spin-lock implementation on ARM.
Next
From: Jeff Davis
Date:
Subject: Re: Minor documentation error regarding streaming replication protocol