| From: | Kirk Strauser <kirk(at)strauser(dot)com> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Why would I want to use connection pooling middleware? |
| Date: | 2009-01-15 20:26:04 |
| Message-ID: | BD4EE8C2-BD3F-4840-95CF-B9238B44EA2E@strauser.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jan 15, 2009, at 12:30 PM, Steve Crawford wrote:
> But if your application is designed to work well with pooling, it
> can provide dramatic performance benefits.
I think that's the problem. As I mentioned at one point, a lot of our
applications have connections open for hours at a time and fire off
queries when the user does something. I'm coming to think that
pooling wouldn't give much benefit to long-living processes like that.
On a related note, is max_connections=400 reasonably sized for a
server with 8GB of RAM? Again, most of these are dormant at any given
time. The database itself is currently hosted on a dual Xeon server
with 3GB of RAM and other applications so I'm sure the new 8-core/8GB
hardware is bound to do better at any rate.
--
Kirk Strauser
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Long | 2009-01-15 20:28:54 | Re: Vacuum and Reindex hangs |
| Previous Message | Raymond O'Donnell | 2009-01-15 20:23:53 | Re: Vacuum and Reindex hangs |