| From: | David Christensen <david(dot)christensen(at)crunchydata(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] pgbench: add multiconnect option |
| Date: | 2022-03-22 15:40:09 |
| Message-ID: | CAOxo6XJJDfXqwBvuAbuq1cjKksHdm1D9A7Wihgox1xKb2C+t8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 19, 2022 at 11:43 AM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>
> Hi Sami,
>
> > Pgbench is a simple benchmark tool by design, and I wonder if adding
> > a multiconnect feature will cause pgbench to be used incorrectly.
>
> Maybe, but I do not see how it would be worse that what pgbench already
> allows.
>
I agree that pgbench is simple; perhaps really too simple when it comes to
being able to measure much more than basic query flows. What pgbench does
have in its favor is being distributed with the core distribution.
I think there is definitely space for a more complicated benchmarking tool
that exercises more scenarios and more realistic query patterns and
scenarios. Whether that is distributed with the core is another question.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-22 15:42:01 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |
| Previous Message | Robert Haas | 2022-03-22 15:37:57 | Re: refactoring basebackup.c (zstd workers) |