From: Manfred Koizar <mkoi-pg@aon.at>
To: Jianshuo Niu <jniu@wc-group.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Help on my database performance
Date: Thu, 31 Jul 2003 21:13:07 +0200
Message-ID: <97qiivonvj5brg9q7ale1033fp53rupi54@4ax.com> (raw)
In-Reply-To: <bgbbaa$bvt$1@main.gmane.org>
References: <bgbbaa$bvt$1@main.gmane.org>
On Thu, 31 Jul 2003 11:06:09 -0400, "Jianshuo Niu" <jniu@wc-group.com>
wrote:
>I ran the same explain analyze on two similar tables. However, the table
>with less data took much more time than the one with more data. Could anyone
>tell me what happened?
>Seq Scan on tfd_catalog (cost=0.00..43769.82 rows=161282 width=10) (actual
>time=3928.64..12905.76 rows=161282 loops=1)
>Total runtime: 13240.21 msec
>
>Seq Scan on hm_catalog (cost=0.00..22181.18 rows=277518 width=9) (actual
>time=21.32..6420.76 rows=277518 loops=1)
>Total runtime: 6772.95 msec
The first SELECT takes almost twice the time because tfd_catalog has
almost twice as many pages than hm_catalog. This may be due to having
wider tuples or more dead tuples in tfd_catalog.
In the former case theres not much you can do.
But the high startup cost of the first SELECT is a hint for lots of
dead tuples. So VACUUM FULL ANALYSE might help.
Servus
Manfred
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: mkoi-pg@aon.at, jniu@wc-group.com
Subject: Re: Help on my database performance
In-Reply-To: <97qiivonvj5brg9q7ale1033fp53rupi54@4ax.com>
References: <bgbbaa$bvt$1@main.gmane.org> <97qiivonvj5brg9q7ale1033fp53rupi54@4ax.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