Re: Re: [GENERAL] PHPBuilder article -- Postgres vs MySQL

Tom Samplonius <tom@sdf.com>

From: Tom Samplonius <tom@sdf.com>
To: carl garland <carlhgarland@hotmail.com>
Cc: martin@math.unl.edu.ar, RDNELSON@co.centre.pa.us, davidb@vectormath.com, mfork@toledolink.com, poulc@cs.auc.dk, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org
Date: 2000-11-15T17:27:48Z
Lists: pgsql-hackers
On Wed, 15 Nov 2000, carl garland wrote:

> >perhaps why, even at 5 clients, the page views he shows never went 
> >significantly above 10/sec?
> 
> I think alot of it has to do with the web server/db setup not pg.  They are 
> using Apache/PHP and looking at their code every page has the additional 
> overhead of making the db connection.  Now if they had used AOLserver with 
> its persistent db connecction pooling scheme they may have faired better ;)

  I doubt it.  PostgreSQL has a higher connection startup overhead than
MySQL, so if every view required a new database connection, it would been
quite a detriment to the PostgreSQL scores.

  PHP can maintain persisitant connections.  Unfortunately, this means
that you end up with a database connection per httpd process.  That really
isn't a problem for PostgreSQL though, it just requires sufficent memory.  
No doubt that is what was being done.

  AOLServer isn't the only system that can pool database connections, so
can servlets/JSP, ColdFusion, ASP, etc.  No doubt AOLServer would be more
widely accepted if it used something other than TCL.

Tom