Hi!
On Mon, Sep 7, 2020 at 1:12 AM Zidenberg, Tsahi <tsahee@amazon.com> wrote:
> First, I apologize for taking so long to answer. This e-mail regretfully got lost in my inbox.
>
> On 24/07/2020, 4:17, "Andres Freund" <andres@anarazel.de> wrote:
>
> > What does "not significantly affected" exactly mean? Could you post the
> > raw numbers?
>
> The following tests show benchmark behavior on m6g.8xl instance (32-core with LSE support)
> and a1.4xlarge (16-core, no LSE support) with and without the patch, based on postgresql 12.4.
> Tests are pgbench select-only/simple-update, and sysbench read-only/write only.
>
> . select-only. simple-update. read-only. write-only
> m6g.8xlarge/vanila. 482130. 56275. 273327. 33364
> m6g.8xlarge/patch. 493748. 59681. 262702. 33024
> a1.4xlarge/vanila. 82437. 13978. 62489. 2928
> a1.4xlarge/patch. 79499. 13932. 62796. 2945
>
> Results obviously change with OS / parameters /etc. I have attempted ensure a fair comparison,
> But I don't think these numbers should be taken as absolute.
> As reference points, m6g instance compiled with -march=native flag, and m5g (x86) instances:
>
> m6g.8xlarge/native. 522771. 60354. 261366. 33582
> m5.8xlarge. 362908. 58732. 147730. 32750
I'd like to resurrect this thread, if there is still interest from
your side. What number of clients and jobs did you use with pgbench?
I've noticed far more dramatic effect on high number of clients.
Could you verify that?
https://akorotkov.github.io/blog/2021/04/30/arm/
------
Regards,
Alexander Korotkov
