Skip site navigation (1) Skip section navigation (2)

Re: Connection Pooling....an interesting question!! (was..Connection Pooling...(Repost)...please do help...)

From: "" <npdavis(at)hotmail(dot)com>
To: aalang(at)rutgersinsurance(dot)com
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Connection Pooling....an interesting question!! (was..Connection Pooling...(Repost)...please do help...)
Date: 2000-12-19 18:45:35
Message-ID: F128BvRnfvcySa4k3z6000035ec@hotmail.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
<html><DIV>
<P>Adam,</P>
<P>Great point. This resounds with a much louder truth when you consider that the reality of expansion is that it usually ends up being 10x bigger than the wildest dreams of the person who is doing the original development. If you think this way, your apps, and database server,&nbsp;will have use well into the future, instead of being re-architected and redesigned later (with you being cursed for designing it poorly). </P>
<P>Of course, you are limited by your budget. Even if you need to use P90 handmedowns (for the extra boxes your boss won't buy)&nbsp;right now to architect&nbsp;it right, when expansion time comes, your app, and budget will be ready to grow the system. Do it right the first time and leave a mark! </P>
<P>I didn't post this to the list because it is sort of off the thread and I don't believe that Oleg wants to hear that he is doing things the dangerous way.</P>
<P>thx,</P>
<P>Neil<BR><BR></P></DIV>
<DIV></DIV>
<DIV></DIV>&gt;From: "Adam Lang" <AALANG(at)RUTGERSINSURANCE(dot)COM>
<DIV></DIV>&gt;CC: <PGSQL-INTERFACES(at)POSTGRESQL(dot)ORG>
<DIV></DIV>&gt;Subject: Re: [INTERFACES] Connection Pooling....an interesting question!! (was..Connection Pooling...(Repost)...please do help...) 
<DIV></DIV>&gt;Date: Sat, 16 Dec 2000 12:36:06 -0500 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;I'm not saying anything about postgres not being able to handle that many 
<DIV></DIV>&gt;connections. I'm just saying it shouldn't if it doesn't have to. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Adam Lang 
<DIV></DIV>&gt;Systems Engineer 
<DIV></DIV>&gt;Rutgers Casualty Insurance Company 
<DIV></DIV>&gt;http://www.rutgersinsurance.com 
<DIV></DIV>&gt;----- Original Message ----- 
<DIV></DIV>&gt;From: "Oleg Bartunov" <OLEG(at)SAI(dot)MSU(dot)SU>
<DIV></DIV>&gt;To: "Adam Lang" <AALANG(at)RUTGERSINSURANCE(dot)COM>
<DIV></DIV>&gt;Cc: <PGSQL-INTERFACES(at)POSTGRESQL(dot)ORG>
<DIV></DIV>&gt;Sent: Saturday, December 16, 2000 12:28 PM 
<DIV></DIV>&gt;Subject: Re: [INTERFACES] Connection Pooling....an interesting question!! 
<DIV></DIV>&gt;(was..Connection Pooling...(Repost)...please do help...) 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; &gt; On Sat, 16 Dec 2000, Adam Lang wrote: 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; &gt; Date: Sat, 16 Dec 2000 12:07:16 -0500 
<DIV></DIV>&gt; &gt; &gt; From: Adam Lang <AALANG(at)RUTGERSINSURANCE(dot)COM>
<DIV></DIV>&gt; &gt; &gt; To: pgsql-interfaces(at)postgresql(dot)org 
<DIV></DIV>&gt; &gt; &gt; Subject: Re: [INTERFACES] Connection Pooling....an interesting 
<DIV></DIV>&gt;question!! (was..Connection Pooling...(Repost)...please do help...) 
<DIV></DIV>&gt; &gt; &gt; 
<DIV></DIV>&gt; &gt; &gt; As (I believe) Joel mentioned, you should use a distributed 
<DIV></DIV>&gt;architecture. 
<DIV></DIV>&gt; &gt; &gt; Clients shouldn't directly access your db server. I believe it is 
<DIV></DIV>&gt; &gt; &gt; "acceptable" if you are only looking at a small app that 10 people are 
<DIV></DIV>&gt;going 
<DIV></DIV>&gt; &gt; &gt; to use, but 200 hundred clients is a lot. 
<DIV></DIV>&gt; &gt; &gt; 
<DIV></DIV>&gt; &gt; &gt; You should have postgres on one tier, your clients on one, and devise a 
<DIV></DIV>&gt; &gt; &gt; middle tier that acts as a relay between your clients and postgres. 
<DIV></DIV>&gt;That 
<DIV></DIV>&gt; &gt; &gt; way the 200 connections are not handled by postgres. Postgres will only 
<DIV></DIV>&gt; &gt; &gt; need to handle the 10 or so you pool with the middle tier. 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; Brrr, we have 128 persistent connections without any problem. 
<DIV></DIV>&gt; &gt; Just use -N option. I dont' remember maximum number of backends compiled 
<DIV></DIV>&gt; &gt; on default, but you could always change this number. 
<DIV></DIV>&gt; &gt; But you're right whe you speaking about 3-tire model. We're experimenting 
<DIV></DIV>&gt; &gt; with Corba and preliminary results are promising 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; Regards, 
<DIV></DIV>&gt; &gt; Oleg 
<DIV></DIV>&gt; &gt; 
<DIV></DIV>&gt; &gt; _____________________________________________________________ 
<DIV></DIV>&gt; &gt; Oleg Bartunov, sci.researcher, hostmaster of AstroNet, 
<DIV></DIV>&gt; &gt; Sternberg Astronomical Institute, Moscow University (Russia) 
<DIV></DIV>&gt; &gt; Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/ 
<DIV></DIV>&gt; &gt; phone: +007(095)939-16-83, +007(095)939-23-83 
<DIV></DIV>&gt; 
<DIV></DIV><br clear=all><hr>Get your FREE download of MSN Explorer at <a href="http://explorer.msn.com">http://explorer.msn.com</a><br></p></html>


Attachment: unknown_filename
Description: text/html (4.4 KB)

pgsql-interfaces by date

Next:From: JosephDate: 2000-12-19 18:56:33
Subject: Help me for "DBI->connect failed: Sorry, too many clients already."
Previous:From: Brian BuhrowDate: 2000-12-19 18:14:36
Subject: Re: Possible memory leak in Postgres V7.0.2/ecpg 2.7.1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group