From: Neil Conway <neilc@samurai.com>
To: david@shadovitz.com <david@shadovitz.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Why is restored database faster?
Date: Wed, 17 Dec 2003 01:00:13 -0500
Message-ID: <87iskgugpe.fsf@mailbox.samurai.com> (raw)
In-Reply-To: <01C3C415.93ADBCE0.david@shadovitz.com>
References: <01C3C415.93ADBCE0.david@shadovitz.com>
David Shadovitz <david@shadovitz.com> writes:
> What could account for this difference?
Lots of things -- disk fragmentation, expired tuples that aren't being
cleaned up by VACUUM due to a long-lived transaction, the state of the
kernel buffer cache, the configuration of the kernel, etc.
> How can I get the original server to perform as well as the new one?
Well, you can start by giving us some more information. For example,
what is the output of VACUUM VERBOSE on the slow server? How much disk
space does the database directory take up on both machines?
(BTW, "SELECT count(*) FROM table" isn't a particularly good DBMS
performance indication...)
-Neil
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: neilc@samurai.com, david@shadovitz.com
Subject: Re: Why is restored database faster?
In-Reply-To: <87iskgugpe.fsf@mailbox.samurai.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