Re: benchmark results comparing versions 15.2 and 16

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: MARK CALLAGHAN <mdcallag(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: benchmark results comparing versions 15.2 and 16
Date: 2023-07-07 13:00:01
Message-ID: 65377ba9-dd24-e4c8-83a3-60cba8b22bf6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello David,

11.05.2023 16:00, Alexander Lakhin wrote:
> Yeah, I see. It's also interesting to me, which tests perform better after
> that commit. It takes several hours to run all tests, so I can't present
> results quickly, but I'll try to collect this information next week.

To my regret, I could not find such tests that week, so I decided to try
later, after reviewing my benchmark running infrastructure.

But for now, as Postgres Pro company graciously shared the benchmarking
infrastructure project [1], it's possible for anyone to confirm or deny my
results. (You can also see which tests were performed and how.)

Having done one more round of comprehensive testing, I still couldn't find
winning tests for commit 3c6fc5820 (but reassured that
test s64da_tpcds.query87 loses a little (and also s64da_tpcds.query38)).
So it seems to me that the tests I performed or their parameters is not
representative enough for that improvement, unfortunately.

[1] https://github.com/postgrespro/pg-mark

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2023-07-07 13:11:39 Standardize type of variable when extending Buffers
Previous Message Hayato Kuroda (Fujitsu) 2023-07-07 12:54:53 RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL