From: Gavin Hamill <gdh@laterooms.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg 8.1.3, AIX, huge box, painfully slow.
Date: Thu, 13 Apr 2006 15:45:42 +0100
Message-ID: <443E6416.3070900@laterooms.com> (raw)
In-Reply-To: <26244.1144683345@sss.pgh.pa.us>
References: <C05C3C44.211A5%llonergan@greenplum.com>
<17613.1144451138@sss.pgh.pa.us>
<1144661209.21409.131.camel@localhost.localdomain>
<443A2856.6050905@laterooms.com>
<26244.1144683345@sss.pgh.pa.us>
Tom Lane wrote:
>Gavin Hamill <gdh@laterooms.com> writes:
>
>
>>would a simple "#define LWLOCK_PADDED_SIZE 128" be sufficient?
>>
>>
>
>Yeah, that's fine.
>
>
OK I tried that but noticed no real improvement... in the interim I've
installed Debian on the pSeries (using
http://debian.gonicus.de/debian/dists/sarge/main/disks-powerpc/current/pseries/install.txt
) and using a simple load-test script - it picks a 'hotelsearch' select
at random from a big file and just does a pg_query on that via PHP...
Using apachebench with 10 clients gave a loadavg of about 10 after a few
minutes, and the logs showed typical query times of 8 seconds. Again, no
disk activity, normal context-switching, just full-out CPU usage...
We're improving the quality + efficiency of the hotelsearch function all
the time (Simon will certainly be able to vouch for its complexity) - am
really uncertain what to do next tho! :/
Cheers,
Gavin.
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-performance@postgresql.org
Cc: gdh@laterooms.com
Subject: Re: pg 8.1.3, AIX, huge box, painfully slow.
In-Reply-To: <443E6416.3070900@laterooms.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