| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Anjan Dave <adave(at)vantage(dot)com> |
| Cc: | Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: can't handle large number of INSERT/UPDATEs |
| Date: | 2004-10-25 21:19:14 |
| Message-ID: | 1098739153.8557.333.camel@home |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2004-10-25 at 16:53, 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
This isn't an index issue, it's a locking issue. Sounds like you have a
bunch of inserts and updates hitting the same rows over and over again.
Eliminate that contention point, and you will have solved your problem.
Free free to describe the processes involved, and we can help you do
that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-10-25 21:30:52 | Re: [PATCHES] ARC Memory Usage analysis |
| Previous Message | Anjan Dave | 2004-10-25 20:53:23 | can't handle large number of INSERT/UPDATEs |