Re: pgbench bug / limitation - Mailing list pgsql-bugs

From Fabien COELHO
Subject Re: pgbench bug / limitation
Date
Msg-id alpine.DEB.2.22.394.2006090941480.274691@pseudo
Whole thread Raw
In response to Re: pgbench bug / limitation  (Fabien COELHO <coelho@cri.ensmp.fr>)
List 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

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16488: psql installation initdb
Next
From: Daniel Gustafsson
Date:
Subject: Re: BUG #16484: pg_regress fails with --outputdir parameter