pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mike Benoit <ipso@snappymail.ca>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Bottleneck
Date: Fri, 06 Aug 2004 10:06:51 -0700
Message-ID: <1091812011.7149.25.camel@ipso.snappymail.ca> (raw)
In-Reply-To: <4110FFF6.1030001@bigfoot.com>
References: <ktQPc.23297$yT2.16983@clgrps13>
	<410FDC53.5080509@bigfoot.com>
	<X0ZPc.23543$yT2.23053@clgrps13>
	<4110FFF6.1030001@bigfoot.com>

On Wed, 2004-08-04 at 17:25 +0200, Gaetano Mendola wrote:

> > The queries themselves are simple, normally drawing information from one 
> > table with few conditions or in the most complex cases using joins on 
> > two table or sub queries.   These behave very well and always have, the 
> > problem is that these queries take place in rather large amounts due to 
> > the dumb nature of the scripts themselves.
> 
> Show us the explain analyze on that queries, how many rows the tables are
> containing, the table schema could be also usefull.
> 

If the queries themselves are optimized as much as they can be, and as
you say, its just the sheer amount of similar queries hitting the
database, you could try using prepared queries for ones that are most
often executed to eliminate some of the overhead. 

I've had relatively good success with this in the past, and it doesn't
take very much code modification.

-- 
Mike Benoit <ipso@snappymail.ca>




view thread (38+ messages)  latest in thread

Message-ID: <1091812011.7149.25.camel@ipso.snappymail.ca>
Permalink:  ../1091812011.7149.25.camel@ipso.snappymail.ca/
Also on:    postgresql.org/message-id/1091812011.7149.25.camel@ipso.snappymail.ca

 · 

reply

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: ipso@snappymail.ca, mendola@bigfoot.com
  Subject: Re: Performance Bottleneck
  In-Reply-To: <1091812011.7149.25.camel@ipso.snappymail.ca>

* 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