| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Bob Dusek <redusek(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: performance config help |
| Date: | 2010-01-11 19:30:20 |
| Message-ID: | dcc563d11001111130g36a750aap8965b3151d245e02@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Jan 11, 2010 at 10:54 AM, Bob Dusek <redusek(at)gmail(dot)com> wrote:
>> You want to use some connection pooling which queues requests when
>> more than some configurable number of connections is already active
>> with a request. You probably want to run that on the server side.
>> As for the postgresql.conf, could you show what you have right now,
>> excluding all comments?
>
> The problem with connection pooling is that we actually have to achieve more
> than 40 per second, which happens to be the sweet spot with our current
> config.
Number of parallel processes doesn't equal # reqs/second. If your
maximum throughput occurs at 40 parallel requests, you'll get more
done reducing the maximum number of concurrent processes to 40 and
letting them stack up in a queue waiting for a spot to run.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob Dusek | 2010-01-11 19:34:44 | Re: performance config help |
| Previous Message | Jaime Casanova | 2010-01-11 19:16:38 | Re: [PERFORMANCE] work_mem vs temp files issue |