Re: Using COPY FREEZE in pgbench

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Using COPY FREEZE in pgbench
Date: 2021-07-06 20:10:02
Message-ID: CAEZATCXFfDaBJpZFJpud4P6sM4BGwBh+JDO6vP5oX4WXgh6c2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 4 Jul 2021 at 09:32, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
>
> >> So overall gain by the patch is around 15%, whereas the last test
> >> before the commit was 14%. It seems the patch is still beneficial
> >> after the commit.
> >
> > Yes, that's good!
>
> Yeah!
>

I tested this with -s100 and got similar results, but with -s1000 it
was more like 1.5x faster:

master:
done in 111.33 s (drop tables 0.00 s, create tables 0.01 s,
client-side generate 52.45 s, vacuum 32.30 s, primary keys 26.58 s)

patch:
done in 74.04 s (drop tables 0.46 s, create tables 0.04 s, client-side
generate 51.81 s, vacuum 2.11 s, primary keys 19.63 s)

Nice!

Regards,
Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-07-06 20:34:09 Re: [PATCH v3 1/1] Fix detection of preadv/pwritev support for OSX.
Previous Message Drouvot, Bertrand 2021-07-06 19:33:35 Re: visibility map corruption