| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, "Jawarilal, Manish" <Manish(dot)Jawarilal(at)dell(dot)com> |
| Subject: | Re: pgbench bug / limitation |
| Date: | 2020-06-09 07:45:58 |
| Message-ID: | alpine.DEB.2.22.394.2006090941480.274691@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> I cannot foresee a setting where over 60 clients per thread (ISTM there is at
> most one wait per client) would make much sense, so let's not help the user
> run ineffective benchmarks. Maybe we should even issue a warning when
> #client/#thread is high. Even if there is a bench where a thread could really
> handle 1000 clients (implying 1000 pg processes server side), probably the
> user could suffer to run that bench with 16 threads.
Here is an attempt at given advice in the doc & a warning when launching.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-doc-threads-1.patch | text/x-diff | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2020-06-09 08:28:32 | Re: BUG #16484: pg_regress fails with --outputdir parameter |
| Previous Message | PG Bug reporting form | 2020-06-09 06:58:43 | BUG #16488: psql installation initdb |