From: Rod Taylor <rbt@rbt.ca>
To: peter <pmcgregor@advso.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Performance issue
Date: Wed, 24 Sep 2003 14:35:50 -0400
Message-ID: <1064428549.20881.20.camel@jester> (raw)
In-Reply-To: <B10D0E1A-EE52-11D7-BD6E-003065E5EDC4@advso.com>
References: <B10D0E1A-EE52-11D7-BD6E-003065E5EDC4@advso.com>
> 20,000 items Takes on average 0.078seconds/room
> 385,000 items Takes on average .11seconds/room
> 690,000 items takes on average .270seconds/room
> 1,028,000 items Takes on average .475seconds/room
>
> As can be seen the time taken to process each room increases. A commit
> occurs when a room has been copied.
It probably isn't the insert that is getting slower, but a select.
Foreign keys to growing tables will exhibit this behaviour.
Since the time is doubling with the number of items, you might want to
check for a SELECT working with a sequential scan rather than an index
scan.
Attachments:
[application/pgp-signature] signature.asc (186B, ../1064428549.20881.20.camel@jester/2-signature.asc)
download
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: rbt@rbt.ca, pmcgregor@advso.com
Subject: Re: Performance issue
In-Reply-To: <1064428549.20881.20.camel@jester>
* 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