Re: can't handle large number of INSERT/UPDATEs - Mailing list pgsql-performance

From Andrew McMillan
Subject Re: can't handle large number of INSERT/UPDATEs
Date
Msg-id 1098823850.6440.89.camel@lamb.mcmillan.net.nz
Whole thread Raw
In response to can't handle large number of INSERT/UPDATEs  ("Anjan Dave" <adave@vantage.com>)
List pgsql-performance
On Mon, 2004-10-25 at 16:53 -0400, Anjan Dave wrote:
> Hi,
>
>
>
> I am dealing with an app here that uses pg to handle a few thousand
> concurrent web users. It seems that under heavy load, the INSERT and
> UPDATE statements to one or two specific tables keep queuing up, to
> the count of 150+ (one table has about 432K rows, other has about
> 2.6Million rows), resulting in ‘wait’s for other queries, and then
> everything piles up, with the load average shooting up to 10+.

Hi,

We saw a similar problem here that was related to the locking that can
happen against referred tables for referential integrity.

In our case we had referred tables with very few rows (i.e. < 10) which
caused the insert and update on the large tables to be effectively
serialised due to the high contention on the referred tables.

We changed our app to implement those referential integrity checks
differently and performance was hugely boosted.

Regards,
                    Andrew.
-------------------------------------------------------------------------
Andrew @ Catalyst .Net .NZ  Ltd,  PO Box 11-053, Manners St,  Wellington
WEB: http://catalyst.net.nz/            PHYS: Level 2, 150-154 Willis St
DDI: +64(4)803-2201      MOB: +64(272)DEBIAN      OFFICE: +64(4)499-2267
                        Chicken Little was right.
-------------------------------------------------------------------------


Attachment

pgsql-performance by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: Sequential Scan with LIMIT
Next
From: "Anjan Dave"
Date:
Subject: Re: can't handle large number of INSERT/UPDATEs