From: Matthew Wakeling <matthew@flymine.org>
To: andrew klassen <aptklassen@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: insert/update tps slow with indices on table > 1M rows
Date: Wed, 4 Jun 2008 11:31:22 +0100 (BST)
Message-ID: <Pine.LNX.4.64.0806041127350.3987@aragorn.flymine.org> (raw)
In-Reply-To: <691681.3510.qm@web37304.mail.mud.yahoo.com>
References: <691681.3510.qm@web37304.mail.mud.yahoo.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: matthew@flymine.org, aptklassen@yahoo.com
Subject: Re: insert/update tps slow with indices on table > 1M rows
In-Reply-To: <Pine.LNX.4.64.0806041127350.3987@aragorn.flymine.org>
References: <691681.3510.qm@web37304.mail.mud.yahoo.com> <Pine.LNX.4.64.0806041127350.3987@aragorn.flymine.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox