From: Richard Huxton <dev@archonet.com>
To: Eliot Gable <egable+pgsql-performance@gmail.com>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Tuning Large PL/PGSQL Stored Procedure
Date: Fri, 26 Mar 2010 12:18:25 +0000
Message-ID: <4BACA611.8050607@archonet.com> (raw)
In-Reply-To: <bf6923ed1003252056m4c40660em6c7d92fc3a917e0c@mail.gmail.com>
References: <bf6923ed1003231400x6c9a6166me835385568851ea@mail.gmail.com>
<b42b73151003251900k6cfe4bc8j7a6b796039482a22@mail.gmail.com>
<bf6923ed1003252056m4c40660em6c7d92fc3a917e0c@mail.gmail.com>
On 26/03/10 03:56, Eliot Gable wrote:
>
> I really am chasing milliseconds here, and I appreciate all your feedback.
> You've given me a relatively large number of possible optimizations I can
> try out. I will definitely try out the libpqtypes. That sounds like a
> promising way to further cut down on execution time. I think most of my
> performance penalty is in transfering the results back to the C++
> application.
In addition to all of Merlin's good advice, if the client is on a
different machine to the server then try sticking wireshark or similar
onto the connection. That should make it pretty clear where the main
costs are in getting your data back.
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, egable+pgsql-performance@gmail.com, mmoncure@gmail.com
Subject: Re: Performance Tuning Large PL/PGSQL Stored Procedure
In-Reply-To: <4BACA611.8050607@archonet.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