pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Kerr <dmk@mr-paradox.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pgbench could not send data to client: Broken pipe
Date: Wed, 8 Sep 2010 13:44:43 -0700
Message-ID: <20100908204443.GG49941@mr-paradox.net> (raw)
In-Reply-To: <9771.1283978128@sss.pgh.pa.us>
References: <20100908174629.GD40339@mr-paradox.net>
	<8037.1283973026@sss.pgh.pa.us>
	<4C87E3A6.8060800@2ndquadrant.com>
	<20100908195654.GB49941@mr-paradox.net>
	<9771.1283978128@sss.pgh.pa.us>

On Wed, Sep 08, 2010 at 04:35:28PM -0400, Tom Lane wrote:
- 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
- 

ah that's a good idea, i'll have to give that a shot.

Actually, this is real.. that's 2000 connections - connection pooled out to 
20k or so. (although i'm pushing for closer to 1000 connections).

I know that's not the ideal way to go, but it's what i've got to work with.

It IS a huge box though...

Thanks

Dave



view thread (19+ messages)  latest in thread

Message-ID: <20100908204443.GG49941@mr-paradox.net>
Permalink:  ../20100908204443.GG49941@mr-paradox.net/
Also on:    postgresql.org/message-id/20100908204443.GG49941@mr-paradox.net

 · 

reply

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: dmk@mr-paradox.net, tgl@sss.pgh.pa.us, greg@2ndquadrant.com
  Subject: Re: pgbench could not send data to client: Broken pipe
  In-Reply-To: <20100908204443.GG49941@mr-paradox.net>

* 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