Tom Lane wrote:
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.
I thought the OP was talking about HTTP connections/s. He didn't say if he
was using persistent database connections or not (obviously better if so).
If it were the case that his setup is new backend launch rate-limited, then
wouldn't the machine show CPU saturation ? (he said it didn't).
