Re: pgbench unable to scale beyond 100 concurrent connections - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: pgbench unable to scale beyond 100 concurrent connections
Date
Msg-id CAMkU=1ycvVFFSyQO6x=kn+7umbxBh1vJZUdPvhNOsWGQu1WErg@mail.gmail.com
Whole thread Raw
In response to Re: pgbench unable to scale beyond 100 concurrent connections  (Sachin Kotwal <kotsachin@gmail.com>)
List pgsql-hackers
On Wed, Jun 29, 2016 at 5:36 AM, Sachin Kotwal <kotsachin@gmail.com> wrote:
> Hi Fabien,
>
> Sorry for very short report.
> I feel pgbench is not so complex tool.
>
> Please see below answers to your questions.
>
>
> On Wed, Jun 29, 2016 at 5:07 PM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
>>
>>
>> Hello Sachin,
>>
>> Your report is very imprecise so it is hard to tell anything.
>>
>> What version of client and server are you running?
>
> I am testing it with 9.6-beta1 binaries. For server and client it is same.
> I am using pgbench on top of postgres_fdw.

That seems like a pretty important bit of info, there.

..

> postgresql does not give any error.

Surely it does.  Perhaps you are not looking in the correct log file.

>
> pgbench says:
> client 36 aborted in state 2: ERROR:  could not connect to server "server_1"
> DETAIL:  FATAL:  sorry, too many clients already

The error is probably coming from the remote side of the FDW, and then
getting passed from there to the direct server, and from there to
pgbench.

Cheers,

Jeff



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Protocol buffer support for Postgres
Next
From: Robert Haas
Date:
Subject: Re: bug in citext's upgrade script for parallel aggregates