pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: Some vacuum & tuning help
Date: Tue, 05 Aug 2003 18:05:26 +0530
Message-ID: <3F2FF1E6.10579.651E89@localhost> (raw)
In-Reply-To: <Pine.BSF.4.44.0308050802180.68903-100000@torgo.978.org>

On 5 Aug 2003 at 8:09, Jeff wrote:

> I've been trying to search through the archives, but it hasn't been
> successful.
> 
> We recently upgraded from pg7.0.2 to 7.3.4 and things were happy. I'm
> trying to fine tune things to get it running a bit better and I'm trying
> to figure out how vacuum output correlates to tuning parameters.
> 
> Here's the msot recent vacuum for the "active" table.  It gets a few
> hundred updates/inserts a minute constantly throughout the day.

I would suggest autovacuum daemon which is in CVS contrib  works for 7.3.x as 
well.. Or schedule a vacuum analyze every 15 minutes or so..
> 
> INFO:  Pages 27781: Changed 0, Empty 0; Tup 2451648: Vac 0, Keep 0, UnUsed
> 1003361.
>         Total CPU 2.18s/0.61u sec elapsed 2.78 sec.
> 
> I see unused is quite high. This morning I bumped max_fsm_pages to 500000.
> If I'm thinking right you want unused and max_fsm to be closish, right?
> (Yesterday it was down around.. oh.. 600k?)
> 
> I'm thinking vacuum full's may be in order. Which stinks because I was
> hoping to do away with the db essentially down for 10 minutes (includes
> all the db's on that machine) while it vacuum'd.

I think vacuum full is required.
 
> The upside is: it is performing great.  During the vacuum analyze I do get
> a few multi-second pauses while something occurs. I figured it was a
> checkpoint, so I bumped checkpoint_timeout to 30 seconds and wal_buffers
> to 128. (I'm just guessing on wal_buffers).

If it is couple of tables that are that heavily killed, I would suggest to a 
pg_dump, drop table and reload table. That should take less time. Your downtime 
might not be 10 minutes but more like 15 say. That's a rough estimate..

> 
> Machine is weenucks 2.2.17 on a dual p3 800, 2gb ram, 18gb drive (mirrored).

You mean linux? I guess you need a kernel revision for a long time. How about 
2.4.21?

> If you guys need other info (shared_buffers, etc) I'll be happy to funish
> them. but the issue isn't query slowness.. just want to get this thing
> oiled).

See if this helps..

Bye
 Shridhar

--
QOTD:	"I thought I saw a unicorn on the way over, but it was just a	horse with 
one of the horns broken off."




view thread (26+ messages)  latest in thread

Message-ID: <3F2FF1E6.10579.651E89@localhost>
Permalink:  ../3F2FF1E6.10579.651E89@localhost/
Also on:    postgresql.org/message-id/3F2FF1E6.10579.651E89@localhost

 · 

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: shridhar_daithankar@persistent.co.in
  Subject: Re: Some vacuum & tuning help
  In-Reply-To: <3F2FF1E6.10579.651E89@localhost>
  References: <Pine.BSF.4.44.0308050802180.68903-100000@torgo.978.org> <3F2FF1E6.10579.651E89@localhost>

* 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