From: | Alastair Turner <bell(at)ctrlf5(dot)co(dot)za> |
---|---|
To: | renier <renier(at)vvconsult(dot)co(dot)za> |
Cc: | jnbpug(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Tweaking |
Date: | 2010-04-09 12:44:27 |
Message-ID: | j2o24e589521004090544j51b615e7x26fb7cf3052b4f75@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | jnbpug |
On Fri, Apr 9, 2010 at 1:58 PM, renier <renier(at)vvconsult(dot)co(dot)za> wrote:
> I would fully agree with your statement looking at the figures now. The results are from PGAdmin, just running the query.
> What really puzzled me, is that it took 4 times longer running the query on the local pgadmin, than it takes to run it over the network. After running the explain analyse query, the speeds improved a lot. But I could not simulate those speeds again. They are back to > 200000ms, even after running Explain Analyse. It seems I cannot get a constant speed.
>
Ok, now we're looking at the specific issue - why does the local
loopback take forever?. A couple more questions:
- What address are you using to connect to the database host from
itself, does it perform the same for the other addresses?
- What is the execution time for the query and iterating through the
resultset from your scripting language - how does it differ between
machines?
- Is this query really representative of what your application does with the db?
Bell
From | Date | Subject | |
---|---|---|---|
Next Message | renier | 2010-04-09 13:15:30 | Re: PostgreSQL Tweaking |
Previous Message | renier | 2010-04-09 11:58:01 | Re: PostgreSQL Tweaking |