RE: track_planning causing performance regression

From: "Tharakan, Robins" <tharar(at)amazon(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: "Massey, Sean" <mssysm(at)amazon(dot)com>
Subject: RE: track_planning causing performance regression
Date: 2020-09-16 10:55:04
Message-ID: abd68940967343acb92f9554688809a4@EX13D05UWC001.ant.amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> During fully-cached SELECT-only test using pgbench, Postgres v13Beta1
> shows ~45% performance drop [2] at high DB connection counts (when
> compared with v12.3)

It'd be great if we could also give credit to "Sean Massey" for this find.

This study on performance regression was done after his (internal) triaging
that the v13 regression disappeared before this commit.

I regret the omission in the original post.
-
thanks
robins

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lauri Svan 2020-09-16 11:34:26 Extending array intersection ops to bloom indexes
Previous Message Taiga KATAYAMA 2020-09-16 09:58:58 Re: Proposal of new PostgreSQL Extension - PGSpiderExt