Tom Lane wrote:
I thought the OP was talking about HTTP connections/s. He didn't say if he[EMAIL PROTECTED] 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. 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). |
- Re: [PERFORM] scaling up postgres Jim C. Nasby
- Re: [PERFORM] scaling up postgres John Vincent
- Re: [PERFORM] scaling up postgres Tom Lane
- Re: [PERFORM] scaling up postgres Scott Marlowe
- Re: [PERFORM] scaling up postgres Gavin Hamill
- Re: [PERFORM] scaling up postgres Markus Schaber
- Re: [PERFORM] scaling up postgres PFC
- Re: [PERFORM] scaling up postgres David Boreham
- Re: [PERFORM] scaling up postgres Tom Lane
- Re: [PERFORM] scaling up postgres David Boreham
- Re: [PERFORM] scaling up postgres Neil Saunders
- Re: [PERFORM] scaling up postgres Markus Schaber