DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=KIGbOvI4acU4tVFuBeFwmYERfXYyNUouazAZo9RkjVRpyxu2JSEs4epwdsA5BRLZH4
	OpD4C2KjHIuwMvX/gzbYqmR3y725UHzYDyvyDLQhTB1n08zLBkpD8agdcbzqZZAMlTNX
	kB0UWokYRTw+idgbhZu8IFJZ3rRV8rVB/wkOM=
Message-ID: <dcc563d10810141144s99c82f7v4d98119f4df1649e@mail.gmail.com>
Date: Tue, 14 Oct 2008 12:44:43 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "=?ISO-8859-1?Q?Mikkel_H=F8gh?=" <mikkel@hoegh.org>
Subject: Re: Drupal and PostgreSQL - performance issues?
Cc: pgsql-general@postgresql.org
In-Reply-To: <C6449FCD-198D-4A04-BACB-1BB2F20DD5B1@hoegh.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <a93e6cbe-0000-4000-9a34-4db3620c619d@mm>
	<C6449FCD-198D-4A04-BACB-1BB2F20DD5B1@hoegh.org>

On Tue, Oct 14, 2008 at 12:39 PM, Mikkel H=F8gh <mikkel@hoegh.org> wrote:
> On 14/10/2008, at 20.23, Daniel Verite wrote:
>>
>> What I've noticed on drupal-6.4 with Ubuntu 8.04 is that the default
>> postgresql.conf has:
>> ssl=3Dtrue
>> and since drupal doesn't allow connecting to pgsql with unix socket path=
s
>> [1], what you get by default is probably TCP + SSL encryption.
>> A crude test that just connects and disconnect to a local pg server
>> appears to me to be 18 times faster when SSL is off.
>> So you might want to check if setting ssl to false makes a difference fo=
r
>> your test.
>
> Ouch, there's a gotcha. So enabling SSL gives you SSL connections by
> default, even for localhost? That's=85 unexpected.
>
>> [1] A patch has been posted here: http://drupal.org/node/26836 , but it
>> seems to have gotten nowhere. The comments about pg_connect() are
>> depressingly lame, apparently nobody had a clue how unix socket files sh=
ould
>> be specified, including the contributor of the patch!
>
> Well, I suppose no one thought about looking at a specific path instead o=
f
> just the default location. That's what we do for MySQL as well. I suppose
> that is a bit silly, but that, too, is going away in Drupal 7 (and I won'=
t
> miss it). It will do the Drupal project a lot of good not having to maint=
ain
> its own database abstraction system.
>
> I'm going to run the test again without SSL to see how much difference it
> does. Thanks for the tip.

Also, look at setting up memcached.  It makes a world of difference.