| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | peter <pmcgregor(at)advso(dot)com> |
| Cc: | Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Performance issue |
| Date: | 2003-09-24 18:35:50 |
| Message-ID: | 1064428549.20881.20.camel@jester |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2003-09-24 21:24:14 | upping checkpoints on production server |
| Previous Message | Sean Chittenden | 2003-09-24 17:47:21 | Re: Performance issue |