pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonah H. Harris <jonah.harris@gmail.com>
To: Carlos Moreno <moreno_pg@mochima.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Possible explanations for catastrophic performace deterioration?
Date: Sun, 23 Sep 2007 12:56:35 -0400
Message-ID: <36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com> (raw)
In-Reply-To: <46F6981B.1010600@mochima.com>
References: <46F6981B.1010600@mochima.com>

You didn't specify the database size, but my guess is that the total
data size about enough to fit in shared_buffers or kernel cache.  On
the new system (or dropped/recreated database), it would've all or
mostly fit in memory which would make things like count(*) work
quickly.  On the old database, you probably had a lot of fragmentation
which would've caused significantly more I/O to be performed thereby
causing a slowdown.  You could compare relation sizes to check easily.

My guess is that a vacuum full would've brought the other database
back up to speed.  In the future, you probably want to set fillfactor
to a reasonable amount to account for updates-to-blocks-between-vacuum
to try and capture as few row-migrations as possible.
-- 
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation                | fax: 732.331.1301
499 Thornall Street, 2nd Floor          | jonah.harris@enterprisedb.com
Edison, NJ 08837                        | http://www.enterprisedb.com/



view thread (12+ messages)  latest in thread

Message-ID: <36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com>
Permalink:  ../36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com/
Also on:    postgresql.org/message-id/36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com

 · 

reply

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: jonah.harris@gmail.com, moreno_pg@mochima.com
  Subject: Re: Possible explanations for catastrophic performace deterioration?
  In-Reply-To: <36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com>
  References: <46F6981B.1010600@mochima.com> <36e682920709230956p1312745eif1c6ba7a342dae3d@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