Re: How to keep queries low latency as concurrency increases - Mailing list pgsql-performance

From Shaun Thomas
Subject Re: How to keep queries low latency as concurrency increases
Date
Msg-id 508FDDF4.2000403@optionshouse.com
Whole thread Raw
In response to Re: How to keep queries low latency as concurrency increases  ("Kevin Grittner" <kgrittn@mail.com>)
List pgsql-performance
On 10/30/2012 06:55 AM, Kevin Grittner wrote:

> Is there a good transaction-based connection pooler in Python?
> You're better off with a good pool built in to the client application
> than with a good pool running as a separate process between the
> client and the database, IMO.

Could you explain this a little more? My experience is almost always the
exact opposite, especially in large clusters that may have dozens of
servers all hitting the same database. A centralized pool has much less
duplication and can serve from a smaller pool than having 12 servers
each have 25 connections reserved in their own private pool or something.

I mean... a pool is basically a proxy server. I don't have 12 individual
proxy servers for 12 webservers.

--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


pgsql-performance by date:

Previous
From: Shaun Thomas
Date:
Subject: Re: Seq scan on 10million record table.. why?
Next
From: Віталій Тимчишин
Date:
Subject: Re: Seq scan on 10million record table.. why?