From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Joseph Bove <jbove@vetstar.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Inconsistent performance
Date: Mon, 15 Sep 2003 15:49:10 -0700 (PDT)
Message-ID: <20030915154131.I76677@megazone.bigpanda.com> (raw)
In-Reply-To: <5.1.0.14.2.20030915182422.00a8a2d8@mail.vetstar.com>
References: <5.1.0.14.2.20030915182422.00a8a2d8@mail.vetstar.com>
On Mon, 15 Sep 2003, Joseph Bove wrote:
> Stephan,
>
> Actually, it's inconsistent with the exact same command. I've now
> replicated the problem by doing the following command:
>
> select count (*) from table;
>
> The table in question has 88899 rows.
>
> The response time is anywhere from 1 second to 12 seconds. Different
> response times can occur in the same minute of testing!
Well, that's really only got one valid plan right now (seqscan and
aggregate). It'd be mildly interesting to see what explain analyze says in
slow and fast states, although I'd be willing to bet that it's just going
to effectively show that the seqscan is taking more or less time.
I think we're going to need to see the configuration settings for the
server and possibly some info on how big the table is (say relpages for
the pg_class row associated with the table after a vacuum full).
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: sszabo@megazone.bigpanda.com, jbove@vetstar.com
Subject: Re: Inconsistent performance
In-Reply-To: <20030915154131.I76677@megazone.bigpanda.com>
References: <5.1.0.14.2.20030915182422.00a8a2d8@mail.vetstar.com> <20030915154131.I76677@megazone.bigpanda.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