From: Tom Lane <tgl@sss.pgh.pa.us>
To: fzied@planet.tn
Cc: pgsql-performance@postgresql.org
Subject: Re: scaling up postgres
Date: Sat, 03 Jun 2006 11:12:38 -0400
Message-ID: <15971.1149347558@sss.pgh.pa.us> (raw)
In-Reply-To: <200606030931.k539V38Y007877@smtp2.planet.net.tn>
References: <200606030931.k539V38Y007877@smtp2.planet.net.tn>
fzied@planet.tn writes:
> I'm using httperf/autobench for measurments and the best result I can get
> is that my system can handle a trafiic of almost 1600 New con/sec.
As per PFC's comment, if connections/sec is a bottleneck for you then
the answer is to use persistent connections. Launching a new backend
is a fairly heavyweight operation in Postgres. It sounds like there
may be some system-level constraints affecting the process creation
rate as well, but it's silly to spend a lot of effort on this when
you can so easily go around the problem.
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, fzied@planet.tn
Subject: Re: scaling up postgres
In-Reply-To: <15971.1149347558@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