From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL strugling during high load
Date: Fri, 13 May 2005 15:00:37 +0200
Message-ID: <20050513130037.GB31454@uio.no> (raw)
In-Reply-To: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt>
References: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt>
On Fri, May 13, 2005 at 03:52:38PM +0300, Mindaugas Riauba wrote:
> Tables are not big (20000-150000 rows each) but have very high
> turnover rate - 100+ updates/inserts/deletes/selects per second.
> So contents of database changes very fast. Problem is that when
> pg_autovacuum does vacuum those changes slows down too much.
> And we keep autovacuum quite aggressive (-v 1000 -V 0.5 -a 1000
> -A 0.1 -s 10) to not bloat database and to avoid bigger impact.
> analyze seems not to impact performance too much.
Are you using the bgwriter?
See http://developer.postgresql.org/~wieck/vacuum_cost/ for details.
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com
Subject: Re: PostgreSQL strugling during high load
In-Reply-To: <20050513130037.GB31454@uio.no>
* 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