| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Rhaoni Chiu Pereira <rhaoni(at)sistemica(dot)info>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Low Insert/Update Performance |
| Date: | 2003-10-22 16:27:49 |
| Message-ID: | 200310220927.49451.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
Rhaoni,
> Total runtime: 3.56 msec
> (4 rows)
Well, from that figure it's not the query that's holding you up.
You said that the system bogs down when you're doing a whole series of these
updates, or just one? If the former, then I'm afraid that it's your disk
that's to blame ... large numbers of rapid-fire updates simply won't be fast
on a single IDE disk. Try getting a second disk and moving the transaction
log to it.
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-10-22 16:58:28 | Re: Low Insert/Update Performance |
| Previous Message | Rhaoni Chiu Pereira | 2003-10-22 16:21:37 | Re: [PERFORM] Low Insert/Update Performance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-10-22 16:36:10 | Re: Processors vs Memory |
| Previous Message | Josh Berkus | 2003-10-22 16:23:15 | Re: slow select |