From: npdavis@hotmail.com
To: aalang@rutgersinsurance.com
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Connection Pooling....an interesting question!! (was..Connection Pooling...(Repost)...please do help...)
Date: Tue, 19 Dec 2000 18:45:35
Message-ID: <F128BvRnfvcySa4k3z6000035ec@hotmail.com> (raw)
<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, 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) right now to architect 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>>From: "Adam Lang" <AALANG@RUTGERSINSURANCE.COM>
<DIV></DIV>>CC: <PGSQL-INTERFACES@POSTGRESQL.ORG>
<DIV></DIV>>Subject: Re: [INTERFACES] Connection Pooling....an interesting question!! (was..Connection Pooling...(Repost)...please do help...)
<DIV></DIV>>Date: Sat, 16 Dec 2000 12:36:06 -0500
<DIV></DIV>>
<DIV></DIV>>I'm not saying anything about postgres not being able to handle that many
<DIV></DIV>>connections. I'm just saying it shouldn't if it doesn't have to.
<DIV></DIV>>
<DIV></DIV>>Adam Lang
<DIV></DIV>>Systems Engineer
<DIV></DIV>>Rutgers Casualty Insurance Company
<DIV></DIV>>http://www.rutgersinsurance.com
<DIV></DIV>>----- Original Message -----
<DIV></DIV>>From: "Oleg Bartunov" <OLEG@SAI.MSU.SU>
<DIV></DIV>>To: "Adam Lang" <AALANG@RUTGERSINSURANCE.COM>
<DIV></DIV>>Cc: <PGSQL-INTERFACES@POSTGRESQL.ORG>
<DIV></DIV>>Sent: Saturday, December 16, 2000 12:28 PM
<DIV></DIV>>Subject: Re: [INTERFACES] Connection Pooling....an interesting question!!
<DIV></DIV>>(was..Connection Pooling...(Repost)...please do help...)
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>> > On Sat, 16 Dec 2000, Adam Lang wrote:
<DIV></DIV>> >
<DIV></DIV>> > > Date: Sat, 16 Dec 2000 12:07:16 -0500
<DIV></DIV>> > > From: Adam Lang <AALANG@RUTGERSINSURANCE.COM>
<DIV></DIV>> > > To: pgsql-interfaces@postgresql.org
<DIV></DIV>> > > Subject: Re: [INTERFACES] Connection Pooling....an interesting
<DIV></DIV>>question!! (was..Connection Pooling...(Repost)...please do help...)
<DIV></DIV>> > >
<DIV></DIV>> > > As (I believe) Joel mentioned, you should use a distributed
<DIV></DIV>>architecture.
<DIV></DIV>> > > Clients shouldn't directly access your db server. I believe it is
<DIV></DIV>> > > "acceptable" if you are only looking at a small app that 10 people are
<DIV></DIV>>going
<DIV></DIV>> > > to use, but 200 hundred clients is a lot.
<DIV></DIV>> > >
<DIV></DIV>> > > You should have postgres on one tier, your clients on one, and devise a
<DIV></DIV>> > > middle tier that acts as a relay between your clients and postgres.
<DIV></DIV>>That
<DIV></DIV>> > > way the 200 connections are not handled by postgres. Postgres will only
<DIV></DIV>> > > need to handle the 10 or so you pool with the middle tier.
<DIV></DIV>> >
<DIV></DIV>> > Brrr, we have 128 persistent connections without any problem.
<DIV></DIV>> > Just use -N option. I dont' remember maximum number of backends compiled
<DIV></DIV>> > on default, but you could always change this number.
<DIV></DIV>> > But you're right whe you speaking about 3-tire model. We're experimenting
<DIV></DIV>> > with Corba and preliminary results are promising
<DIV></DIV>> >
<DIV></DIV>> >
<DIV></DIV>> > Regards,
<DIV></DIV>> > Oleg
<DIV></DIV>> >
<DIV></DIV>> > _____________________________________________________________
<DIV></DIV>> > Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
<DIV></DIV>> > Sternberg Astronomical Institute, Moscow University (Russia)
<DIV></DIV>> > Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
<DIV></DIV>> > phone: +007(095)939-16-83, +007(095)939-23-83
<DIV></DIV>>
<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;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: npdavis@hotmail.com, aalang@rutgersinsurance.com
Subject: Re: Connection Pooling....an interesting question!! (was..Connection Pooling...(Repost)...please do help...)
In-Reply-To: <F128BvRnfvcySa4k3z6000035ec@hotmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox