To: Joe <svn@freedomcircle.net>,
	"Magnus Hagander" <mha@sollentuna.net>
Cc: "Gavin Sherry" <swm@alcove.com.au>,
	pgsql-performance@postgresql.org
Subject: Re: Comparative performance
References: <6BCB9D8A16AC4241919521715F4D8BCE92E6D6@algol.sollentuna.se>
	<433BDB0B.8010002@freedomcircle.net>
Message-ID: <op.sxvgnqfrth1vuj@localhost>
Date: Thu, 29 Sep 2005 18:12:52 +0200
From: PFC <lists@boutiquenumerique.com>
Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?=
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <433BDB0B.8010002@freedomcircle.net>
User-Agent: Opera M2/8.0 (Linux, build 1095)


> I just tried using pg_pconnect() and I didn't notice any significant  
> improvement.  What bothers me most is that with Postgres I tend to see  
> jerky behavior on almost every page:  the upper 1/2 or 2/3 of the page  
> is displayed first and you can see a blank bottom (or you can see a  
> half-filled completion bar).  With MySQL each page is generally  
> displayed in one swoop.

	Persistent connections are useful when your page is fast and the  
connection time is an important part of your page time. It is mandatory if  
you want to serve more than 20-50 hits/s without causing unnecessary load  
on the database. This is not your case, which is why you don't notice any  
improvement...