Re: Re: [GENERAL] PHPBuilder article -- Postgres vs MySQL - Mailing list pgsql-hackers

From Tom Samplonius
Subject Re: Re: [GENERAL] PHPBuilder article -- Postgres vs MySQL
Date
Msg-id Pine.BSF.4.05.10011150922000.18177-100000@misery.sdf.com
Whole thread Raw
In response to Re: Re: [GENERAL] PHPBuilder article -- Postgres vs MySQL  ("carl garland" <carlhgarland@hotmail.com>)
Responses Re: Re: [GENERAL] PHPBuilder article -- Postgres vs MySQL  (Don Baccus <dhogaza@pacifier.com>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: WHERE-clause evaluation order (was [BUGS] Problem with BETWEEN and a view)
Next
From: Tom Lane
Date:
Subject: Re: Re: UUNET socket-file-location patch