From: James Mansion <james@mansionfamily.plus.com>
To: Matthew Wakeling <matthew@flymine.org>
Cc: andrew klassen <aptklassen@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: insert/update tps slow with indices on table > 1M rows
Date: Wed, 04 Jun 2008 21:15:45 +0100
Message-ID: <4846F7F1.1050408@mansionfamily.plus.com> (raw)
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>
Matthew Wakeling wrote:
> 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.
That would explain a disappointing upper limit on insert rate, but not
any sort of cliff for the rate. Nor, really, any material slowdown, if
the single thread implies that we're stuck on round trip latency as a
material limiting factor.
James
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: james@mansionfamily.plus.com, matthew@flymine.org, aptklassen@yahoo.com
Subject: Re: insert/update tps slow with indices on table > 1M rows
In-Reply-To: <4846F7F1.1050408@mansionfamily.plus.com>
* 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