Skip site navigation (1) Skip section navigation (2)

Re: time to stop tuning?

From: "David Parker" <dparker(at)tazznetworks(dot)com>
To: "Rod Taylor" <rbt(at)sitesell(dot)com>
Cc: "Postgresql Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: time to stop tuning?
Date: 2004-11-26 19:16:09
Message-ID: 07FDEE0ED7455A48AC42AC2070EDFF7C26BDDF@corpsrv2.tazznetworks.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hi. Thanks for responding.

As it happens, the client-side already has a connection pool. 

We need statistics enabled so that autovacuum can run (without
autovacuum running our updates begin to kill us pretty quickly).

Moving off of Solaris 9 isn't an option, even for the purposes of
comparison, unfortunately.

On limiting the client side connections: we've been gradually pushing up
the client-side connection pool and threads, and have seen steady
improvement in our throughput up to the current barrier we have reached.
I guess the idea would be that backing off on the connections would
allow each operation to finish faster, but that hasn't been the observed
behavior so far. 

I've attached the plans for the 4 queries that represent ~35% of our
load. These are run against the same dataset, but without any other
load. Another big query basically requires a test to be runnning because
the data is transient, and I can't run that at the moment. The times for
the individual queries is really fine - it's just they are called 3
times for every logical "unit of work" on the client side, so they are
called thousands of times in a given test (hence the need for client
caching).

Thanks.

- DAP

>-----Original Message-----
>From: Rod Taylor [mailto:rbt(at)sitesell(dot)com] 
>Sent: Friday, November 26, 2004 1:29 PM
>To: David Parker
>Cc: Postgresql Performance
>Subject: Re: [PERFORM] time to stop tuning?
>
>On Fri, 2004-11-26 at 12:13 -0500, David Parker wrote:
>> 
>> I suspect the ultimate answer to our problem will be:
>> 
>>    1) aggressive client-side caching
>>    2) SQL tuning
>>    3) more backend hardware
>
>#0 might actually be using connection pooling and using cached 
>query plans (PREPARE), disabling the statistics daemon, etc.
>
>For the plans, send us EXPLAIN ANALYZE output for each of the 
>common queries.
>
>If you can try it, I'd give a try at FreeBSD or a newer Linux 
>on your system instead of Solaris. Older versions of Solaris 
>had not received the same amount of attention for Intel 
>hardware as the BSDs and Linux have and I would imagine 
>(having not tested it recently) that this is still true for 
>32bit Intel.
>
>Another interesting test might be to limit the number of 
>simultaneous connections to 8 instead of 30 (client side 
>connection retry) after client side connection pooling via 
>pgpool or similar has been installed.
>
>Please report back with your findings.
>--
>Rod Taylor <rbt(at)sitesell(dot)com>
>
>

Attachment: plan.txt
Description: text/plain (4.5 KB)

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2004-11-26 19:25:34
Subject: Re: Postgres backend using huge amounts of ram
Previous:From: Tom LaneDate: 2004-11-26 19:04:35
Subject: Re: time to stop tuning?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group