pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Benjamin Krajmalnik <kraj@illumen.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: slow cursor
Date: Thu, 20 Apr 2006 22:10:12 -0600
Message-ID: <8511B4970E0D124898E973DF496F9B4357E0F6@stash.stackdump.local> (raw)
References: <6992E470F12A444BB787B5C937B9D4DF0406AD88@ca-mail1.cis.local>

Siriam,
 
I have no clue what it is you are trying to do, but I have a similar situation.  I have a monitoring system which sends data to our psotgresql database.  The system calls a single stored procedure which performs on-the-fly data aggregation for the particular test for which the data is being sent.  You may want to look at some numerical methods books and see if you can do what I am doing.  I keep a record with computed values representing the data up to the previous transaction, and recompute accordingly.  This is done estremely quickly.  Then, twice a day, I run a stored procedure which runs some other aggregations based on the raw data which was sent over.  It was taking about 30 seconds against a table with about 500K records, aggregating to a table with 2K records.  Since not all of the tests need this particular data aggregation, an additional field was added to the test descriptor to flag those tests which need to have the particular aggregation (essentially, computing statistical process control data).  After doing this, our 30 seconds went down to about 2 seconds.
 
I do not have access to our aggregation dunction, but I am using one cursor and 2 record types.
First, I perform a loop on a selection into the record structure for the candidate tests.  Within this loop, I create a cursor which fetches the row data into another record structure.  This record structure now holds the data we need in order to update the table on which the primary loop is running.
 
I do not know if this is the optimum way of doing this within PostgreSQL, but the perofrmance appears to be  fine.  I have not goten into the fine tuning for speed just yet.
 
Just an idea - hope it helps.

________________________________

From: pgsql-admin-owner@postgresql.org on behalf of Sriram Dandapani
Sent: Thu 4/20/2006 9:45 PM
To: Jim C. Nasby
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] slow cursor



Yes..all of it is in one transaction as there is a window of record ids
that need to be processed in 1 transaction. Data inflow is very
voluminous appx 1 million every 15 minutes and the goal is to create
aggregate tables on the fly (the alternative is to use nightly
aggregates).

-----Original Message-----
From: Jim C. Nasby [mailto:jnasby@pervasive.com]
Sent: Thursday, April 20, 2006 7:36 PM
To: Sriram Dandapani
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] slow cursor

On Mon, Apr 17, 2006 at 07:07:54AM -0700, Sriram Dandapani wrote:
> I have a cursor that fetches 150K rows and updates or inserts a table
> with 150K rows.
>
> It takes several minutes for the process to complete (about 15
minutes).
> The select by itself (without cursor) gets all rows in 15 seconds.
>
> Is there a way to optimize the cursor to fetch all records and speed
up
> the process. I still need to do the record by record processing

Not likely. Are you at least doing all this inside a transaction?
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org

view thread (6+ messages)  latest in thread

Message-ID: <8511B4970E0D124898E973DF496F9B4357E0F6@stash.stackdump.local>
Permalink:  ../8511B4970E0D124898E973DF496F9B4357E0F6@stash.stackdump.local/
Also on:    postgresql.org/message-id/8511B4970E0D124898E973DF496F9B4357E0F6@stash.stackdump.local

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: kraj@illumen.com, sdandapani@counterpane.com, jnasby@pervasive.com
  Subject: Re: slow cursor
  In-Reply-To: <8511B4970E0D124898E973DF496F9B4357E0F6@stash.stackdump.local>
  References: <6992E470F12A444BB787B5C937B9D4DF0406AD88@ca-mail1.cis.local> <8511B4970E0D124898E973DF496F9B4357E0F6@stash.stackdump.local>

* 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