pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Lakhin <exclusion@gmail.com>
To: MARK CALLAGHAN <mdcallag@gmail.com>
To: pgsql-hackers@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Subject: Re: benchmark results comparing versions 15.2 and 16
Date: Mon, 8 May 2023 16:00:01 +0300
Message-ID: <b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com> (raw)
In-Reply-To: <CAFbpF8N4bVFZ+eyWFj_+fZXZFSayk2kJVtZnouUVKGHudiDrSw@mail.gmail.com>
References: <CAFbpF8N4bVFZ+eyWFj_+fZXZFSayk2kJVtZnouUVKGHudiDrSw@mail.gmail.com>

Hello Mark,

05.05.2023 20:45, MARK CALLAGHAN wrote:
> This is mostly a hobby project for me - my other hobby is removing invasive weeds. I am happy to answer questions and 
> run more tests, but turnaround for answers won't be instant. Getting results from Linux perf for these tests is on my 
> TODO list. For now I am just re-running a subset of these to get more certainty that the regressions are real and not 
> noise.
>

It's a very interesting topic to me, too. I had developed some scripts to
measure and compare postgres`s performance using miscellaneous public
benchmarks (ycsb, tpcds, benchmarksql_tpcc, htapbench, benchbase, gdprbench,
s64da-benchmark, ...). Having compared 15.3 (56e869a09) with master
(58f5edf84) I haven't seen significant regressions except a few minor ones.
First regression observed with a simple pgbench test:
pgbench -i benchdb
pgbench -c 10 -T 300 benchdb
(with default compilation options and fsync = off)

On master I get:
tps = 10349.826645 (without initial connection time)
On 15.3:
tps = 11296.064992 (without initial connection time)

This difference is confirmed by multiple test runs. `git bisect` for this
regression pointed at f193883fc.

Best regards,
Alexander





view thread (29+ messages)  latest in thread

Message-ID: <b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com>
Permalink:  ../b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com/
Also on:    postgresql.org/message-id/b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: exclusion@gmail.com, mdcallag@gmail.com, andres@anarazel.de
  Subject: Re: benchmark results comparing versions 15.2 and 16
  In-Reply-To: <b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com>
  References: <CAFbpF8N4bVFZ+eyWFj_+fZXZFSayk2kJVtZnouUVKGHudiDrSw@mail.gmail.com> <b32bed1b-0746-9b20-1472-4bdc9ca66d52@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox