From: Kim <kim@myemma.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: unusual performance for vac following 8.2 upgrade
Date: Thu, 11 Jan 2007 17:12:46 -0600
Message-ID: <45A6C46E.3020702@myemma.com> (raw)
In-Reply-To: <6871.1168554415@sss.pgh.pa.us>
References: <45A671CD.1050706@myemma.com>
<27939.1168539652@sss.pgh.pa.us>
<45A68C74.4080405@myemma.com>
<28949.1168544710@sss.pgh.pa.us>
<6871.1168554415@sss.pgh.pa.us>
Our pgstats.stat file is 40M for 8.2, on 8.1 it was 33M. Our schema size
hasn't grown *that* much in the two weeks since we upgraded
I'm not sure if this sheds any more light on the situation, but in
scanning down through the process output from truss, it looks like the
first section of output was a large chunk of reads on pgstat.stat,
followed by a larger chunk of reads on the global directory and
directories under base - this whole section probably went on for a good
6-7 minutes, though I would say the reads on pgstat likely finished
within a couple of minutes or so. Following this there was a phase were
it did a lot of seeks and reads on files under pg_clog, and it was while
doing this (or perhaps it had finished whatever it wanted with clogs) it
dropped into the send()/SIGUSR1 loop that goes for another several minutes.
Kim
Tom Lane wrote:
>I wrote:
>
>
>>(2) Reconsider whether last-vacuum-time should be sent to the collector
>>unconditionally.
>>
>>
>
>Actually, now that I look, the collector already contains this logic:
>
> /*
> * Don't create either the database or table entry if it doesn't already
> * exist. This avoids bloating the stats with entries for stuff that is
> * only touched by vacuum and not by live operations.
> */
>
>and ditto for analyze messages. So my idea that the addition of
>last-vac-time was causing an increase in the statistics file size
>compared to 8.1 seems wrong.
>
>How large is your $PGDATA/global/pgstat.stat file, anyway?
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
>
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: kim@myemma.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: unusual performance for vac following 8.2 upgrade
In-Reply-To: <45A6C46E.3020702@myemma.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