From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Kerr <dmk@mr-paradox.net>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pgbench could not send data to client: Broken pipe
Date: Wed, 08 Sep 2010 16:35:28 -0400
Message-ID: <9771.1283978128@sss.pgh.pa.us> (raw)
In-Reply-To: <20100908195654.GB49941@mr-paradox.net>
References: <20100908174629.GD40339@mr-paradox.net>
<8037.1283973026@sss.pgh.pa.us>
<4C87E3A6.8060800@2ndquadrant.com>
<20100908195654.GB49941@mr-paradox.net>
David Kerr <dmk@mr-paradox.net> writes:
> should i be running pgbench differently? I tried increasing the # of threads
> but that didn't increase the number of backend's and i'm trying to simulate
> 2000 physical backend processes.
The odds are good that if you did get up that high, what you'd find is
pgbench itself being the bottleneck, not the server. What I'd suggest
is running several copies of pgbench *on different machines*, all
beating on the one database server. Collating the results will be a bit
more of a PITA than if there were only one pgbench instance, but it'd
be a truer picture of real-world behavior.
It's probably also worth pointing out that 2000 backend processes is
likely to be a loser anyhow. If you're just doing this for academic
purposes, fine, but if you're trying to set up a real system for 2000
clients you almost certainly want to stick some connection pooling in
there.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, dmk@mr-paradox.net, greg@2ndquadrant.com
Subject: Re: pgbench could not send data to client: Broken pipe
In-Reply-To: <9771.1283978128@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox