pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin <justin@emproshunts.com>
To: Gregory Williamson <Gregory.Williamson@digitalglobe.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: need to speed up query
Date: Tue, 06 May 2008 00:48:29 -0500
Message-ID: <481FF12D.4080600@emproshunts.com> (raw)
In-Reply-To: <8B319E5A30FF4A48BE7EEAAF609DB233015E3832@COMAIL01.digitalglobe.com>
References: <481FBC0D.7010509@emproshunts.com>
	<8B319E5A30FF4A48BE7EEAAF609DB233015E3832@COMAIL01.digitalglobe.com>

Gregory Williamson wrote:
>
> Justin --
>
> You wrote:
> > 
> > i've had to write queries to get trail balance values out of the GL
> > transaction table and i'm not happy with its performance
> >
> >
> > The table has 76K rows growing about 1000 rows per working day so the
> > performance is not that great it takes about 20 to 30 seconds to get all
> > the records for the table and when we limit it to single accounting
> > period it drops down to 2 seconds
>
> So 30 seconds for 76 days (roughly) worth of numbers ? Not terrible 
> but not great.
>
> > Here is the query and explain .  PostgreSql  is 8.3.1 on new server with
> > raid 10 Serial SCSI.
> <... snipped 'cause I have a lame reader ...>
>
not according to the bench marks i have done,  which were posted a 
couple of months ago.
>
>
> > "  Sort Method:  quicksort  Memory: 292kB"
> <...snip...>
> > "Total runtime: 24682.580 ms"
>
>
> I don't have any immediate thoughts but maybe you could post the table 
> schemas and indexes. It looks to my untutored eye as if most of the 
> estimates are fair so I am guessing that you have run analyze recently.
>
> What is your sort memory set to ? If work_mem is too low then you'll 
> go to disk (if you see tmp files under the postgres $PGDATA/base 
> directory you might be seeing the result of this) ...
>
i need to look into work mem its set at 25 megs which is fine for most 
work unless we get into the accounting queries which have to be more 
complicated than they need to be because how some of the tables are laid 
out which i did not lay out.
>
>
> HTH
>
> Greg Williamson
> Senior DBA
> DigitalGlobe
>
> Confidentiality Notice: This e-mail message, including any 
> attachments, is for the sole use of the intended recipient(s) and may 
> contain confidential and privileged information and must be protected 
> in accordance with those provisions. Any unauthorized review, use, 
> disclosure or distribution is prohibited. If you are not the intended 
> recipient, please contact the sender by reply e-mail and destroy all 
> copies of the original message.
>
> (My corporate masters made me say this.)
>

view thread (11+ messages)  latest in thread

Message-ID: <481FF12D.4080600@emproshunts.com>
Permalink:  ../481FF12D.4080600@emproshunts.com/
Also on:    postgresql.org/message-id/481FF12D.4080600@emproshunts.com

 · 

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: justin@emproshunts.com, Gregory.Williamson@digitalglobe.com
  Subject: Re: need to speed up query
  In-Reply-To: <481FF12D.4080600@emproshunts.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