From: Robert Haas <robertmhaas@gmail.com>
To: David Kerr <dmk@mr-paradox.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Very high effective_cache_size == worse performance?
Date: Tue, 20 Apr 2010 14:15:19 -0400
Message-ID: <s2i603c8f071004201115xae430457q88074af464c8964f@mail.gmail.com> (raw)
In-Reply-To: <20100420180351.GA51940@mr-paradox.net>
References: <20100420173936.GA50886@mr-paradox.net>
<h2w603c8f071004201044tbc8ce8fenb846b7643a2b9376@mail.gmail.com>
<20100420180351.GA51940@mr-paradox.net>
On Tue, Apr 20, 2010 at 2:03 PM, David Kerr <dmk@mr-paradox.net> wrote:
> that thought occured to me while I was testing this. I ran a vacuumdb -z
> on my database during the load and it didn't impact performance at all.
The window to run ANALYZE usefully is pretty short. If you run it
before the load is complete, your stats will be wrong. If you run it
after the select statements that hit the table are planned, the
updated stats won't arrive in time to do any good.
> I did turn on log_min_duration_statement but that caused performance to be unbearable,
> but i could turn it on again if it would help.
I think you need to find a way to identify exactly which query is
running slowly. You could sit there and run "select * from
pg_stat_activity", or turn on log_min_duration_statement, or have your
application print out timestamps at key points, or some other
method...
...Robert
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: robertmhaas@gmail.com, dmk@mr-paradox.net
Subject: Re: Very high effective_cache_size == worse performance?
In-Reply-To: <s2i603c8f071004201115xae430457q88074af464c8964f@mail.gmail.com>
References: <20100420173936.GA50886@mr-paradox.net> <h2w603c8f071004201044tbc8ce8fenb846b7643a2b9376@mail.gmail.com> <20100420180351.GA51940@mr-paradox.net> <s2i603c8f071004201115xae430457q88074af464c8964f@mail.gmail.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