| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | andrew klassen <aptklassen(at)yahoo(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: insert/update tps slow with indices on table > 1M rows |
| Date: | 2008-06-04 10:31:22 |
| Message-ID: | Pine.LNX.4.64.0806041127350.3987@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, 3 Jun 2008, andrew klassen wrote:
> Basically, I have a somewhat constant rate of inserts/updates that go
> into a work queue and then get passed to postgres.
> The cpu load is not that high, i.e. plenty of idle cpu. I am running an older
> version of freebsd and the iostat output is not very detailed.
If you're running a "work queue" architecture, that probably means you
only have one thread doing all the updates/inserts? It might be worth
going multi-threaded, and issuing inserts and updates through more than
one connection. Postgres is designed pretty well to scale performance by
the number of simultaneous connections.
Matthew
--
Contrary to popular belief, Unix is user friendly. It just happens to be
very selective about who its friends are. -- Kyle Hearn
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mathieu Gilardet | 2008-06-04 14:02:23 | RAM / Disk ratio, any rule? |
| Previous Message | Scott Marlowe | 2008-06-04 06:02:34 | Re: insert/update tps slow with indices on table > 1M rows |