pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
full vacuum - resources - scaling
3+ messages / 3 participants
[nested] [flat]

* full vacuum - resources - scaling
@ 2006-05-30 13:44  Mr. Dan <bitsandbytes88@hotmail.com>
  0 siblings, 2 replies; 3+ messages in thread

From: Mr. Dan @ 2006-05-30 13:44 UTC (permalink / raw)
  To: pgsql-admin

Hi,

I have noticed that my full vacuum and re-index script is taking a day and a 
half instead of 1/2 day.
Recently, the size of my database cluster has doubled to 130 GB.   Would 
anyone recommend increasing one or more of these to help get my full vacuums 
to run a little faster?

Thanks,
~DjK



work memory       49152 KB
shared buffers      65536 (8 KB)
maxfsmpages       480001 (6 bytes each)
maxfsmrelations    30000 (70 bytes each)

effective cache     983040 (8 KB each)





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: full vacuum - resources - scaling
@ 2006-05-30 14:10  Alvaro Herrera <alvherre@commandprompt.com>
  parent: Mr. Dan <bitsandbytes88@hotmail.com>
  1 sibling, 0 replies; 3+ messages in thread

From: Alvaro Herrera @ 2006-05-30 14:10 UTC (permalink / raw)
  To: Mr. Dan <bitsandbytes88@hotmail.com>; +Cc: pgsql-admin

Mr. Dan wrote:
> Hi,
> 
> I have noticed that my full vacuum and re-index script is taking a day and 
> a half instead of 1/2 day.
> Recently, the size of my database cluster has doubled to 130 GB.   Would 
> anyone recommend increasing one or more of these to help get my full 
> vacuums to run a little faster?

I guess the question is why are you running vacuum full at all.  Plain
vacuum should suffice, provided the FSM settings are enough for your
database:

> maxfsmpages       480001 (6 bytes each)
> maxfsmrelations    30000 (70 bytes each)

max_fsm_pages at 480000 are enough to cover 3 GB, if my math is correct.
It may be enough or it may not, depending on the dynamics of your data.

Also with non-full vacuum you may be able to get away with vacuuming
some tables more often.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: full vacuum - resources - scaling
@ 2006-05-30 14:58  Andrew Sullivan <ajs@crankycanuck.ca>
  parent: Mr. Dan <bitsandbytes88@hotmail.com>
  1 sibling, 0 replies; 3+ messages in thread

From: Andrew Sullivan @ 2006-05-30 14:58 UTC (permalink / raw)
  To: pgsql-admin

On Tue, May 30, 2006 at 09:44:22AM -0400, Mr. Dan wrote:
> Hi,
> 
> I have noticed that my full vacuum and re-index script is taking a day and 
> a half instead of 1/2 day.
> Recently, the size of my database cluster has doubled to 130 GB.   Would 
> anyone recommend increasing one or more of these to help get my full 
> vacuums to run a little faster?

What Alvaro said.  I'll also point out, however, that in my
experience, VACUUM FULL time does not increase linearly with database
size.  I suspect this is because of the cost of reorganising so much
more data, but I haven't done any real analysis of it.

The main thing is, "Don't do vacuum full."

A
-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
		--George Orwell



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2006-05-30 14:58 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-05-30 13:44 full vacuum - resources - scaling Mr. Dan <bitsandbytes88@hotmail.com>
2006-05-30 14:10 ` Alvaro Herrera <alvherre@commandprompt.com>
2006-05-30 14:58 ` Andrew Sullivan <ajs@crankycanuck.ca>

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