From: Mischa Sandberg <mischa.sandberg@telus.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mindaugas Riauba <mind@bi.lt>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL strugling during high load
Date: Fri, 13 May 2005 10:33:22 -0700
Message-ID: <1116005602.4284e4e28869e@webmail.telus.net> (raw)
In-Reply-To: <23217.1115991763@sss.pgh.pa.us>
References: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt>
<23217.1115991763@sss.pgh.pa.us>
Quoting Tom Lane <tgl@sss.pgh.pa.us>:
> "Mindaugas Riauba" <mind@bi.lt> writes:
> > ... So contents of database changes very fast. Problem is that
> when
> > pg_autovacuum does vacuum those changes slows down too much.
>
> The "vacuum cost" parameters can be adjusted to make vacuums fired
> by pg_autovacuum less of a burden. I haven't got any specific
> numbers
> to suggest, but perhaps someone else does.
I solved one problem by cranking sleep scaling to -S 20.
It made pg_autovacuum back off longer during extended periods of heavy
disk-intensive query activity. Our update activity is near-constant
insert rate, then once or twice a day, massive deletes.
--
Dreams come true, not free.
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: mischa.sandberg@telus.net, tgl@sss.pgh.pa.us, mind@bi.lt
Subject: Re: PostgreSQL strugling during high load
In-Reply-To: <1116005602.4284e4e28869e@webmail.telus.net>
* 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