Re: Performance degradation on concurrent COPY into a single relation in PG16.

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Performance degradation on concurrent COPY into a single relation in PG16.
Date: 2023-08-02 01:35:49
Message-ID: CAApHDvpbtpdTdWG5y79Ast-pbEj9YGmD9_zbtTHWv8gisSCL0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2 Aug 2023 at 12:25, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> master @ 3845577cb
> latency average = 1575.879 ms
>
> 6.79% postgres [.] pg_strtoint32_safe
>
> master~1
> latency average = 1968.004 ms
>
> 14.28% postgres [.] pg_strtoint32_safe
>
> REL_16_STABLE
> latency average = 1735.163 ms
>
> 6.04% postgres [.] pg_strtoint32_safe
>
> REL_16_STABLE~1
> latency average = 2188.186 ms
>
> 13.83% postgres [.] pg_strtoint32_safe

And just to complete that set, here's the REL_15_STABLE performance
using the same test:

latency average = 1829.108 ms

15.46% postgres [.] pg_strtoint32

So, it looks like this item can be closed off. I'll hold off from
doing that for a few days just in case anyone else wants to give
feedback or test themselves.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2023-08-02 02:16:35 Re: [PoC] pg_upgrade: allow to upgrade publisher node
Previous Message Andy Fan 2023-08-02 01:05:44 Re: Extract numeric filed in JSONB more effectively