From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, MARK CALLAGHAN <mdcallag(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: benchmark results comparing versions 15.2 and 16 |
Date: | 2023-05-16 00:42:31 |
Message-ID: | ZGLRd9RRx/47BrOP@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 15, 2023 at 05:14:47PM -0700, Andres Freund wrote:
> On 2023-05-15 14:20:24 +0900, Michael Paquier wrote:
>> On Thu, May 11, 2023 at 01:28:40PM +0900, Michael Paquier wrote:
>> Extreme is adapted for a worst-case scenario. Looking at my notes
>> from a few months back, that's kind of what I did on my laptop, which
>> was the only machine I had at hand back then:
>> - Compilation of code with -O2.
>
> I assume without assertions as well?
Yup, no assertions.
> 45k seems too low for a modern machine, given that I get > 80k in such a
> workload, on a workstation with server CPUs (i.e. many cores, but not that
> fast individually). Hence wondering about assertions being enabled...
Nope, disabled.
> I get quite variable performance if I don't pin client / server to the same
> core, but even the slow performance is faster than 45k.
Okay. You mean with something like taskset or similar, I guess?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-05-16 00:54:53 | Re: benchmark results comparing versions 15.2 and 16 |
Previous Message | Michael Paquier | 2023-05-16 00:38:54 | Re: Introduce WAIT_EVENT_EXTENSION and WAIT_EVENT_BUFFER_PIN |