Setting autovacuum_vacuum_scale_factor to 0 a good idea ?

From: Sébastien Lorion <sl(at)thestrangefactory(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Setting autovacuum_vacuum_scale_factor to 0 a good idea ?
Date: 2012-09-14 20:11:05
Message-ID: CAGa5y0Nv==ObEnWr5BbR6mRWPTP21uLwduM2UYs3oxMdy+60sA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I am pondering about this... My thinking is that since *_scale_factor need
to be set manually for largish tables (>1M), why not
set autovacuum_vacuum_scale_factor and autovacuum_analyze_scale_factor, and
increase the value of autovacuum_vacuum_threshold to, say, 10000, and
autovacuum_analyze_threshold
to 2500 ? What do you think ?

Also, with systems handling 8k-10k tps and dedicated to a single database,
would there be any cons to decreasing autovacuum_naptime to say 15s, so
that the system perf is less spiky ?

Sébastien

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Sébastien Lorion 2012-09-14 20:19:28 wal_sync_method on FreeBSD 9.0 - ZFS
Previous Message McKinzie, Alan (Alan) 2012-09-14 15:56:04 Are there known performance issues with defining all Foreign Keys as deferrable initially immediate