From: | Mischa Sandberg <mischa(dot)sandberg(at)telus(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Mindaugas Riauba <mind(at)bi(dot)lt>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: PostgreSQL strugling during high load |
Date: | 2005-05-13 17:33:22 |
Message-ID: | 1116005602.4284e4e28869e@webmail.telus.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Quoting Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Mindaugas Riauba" <mind(at)bi(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | John A Meinel | 2005-05-13 18:32:42 | Re: Optimize complex join to use where condition before |
Previous Message | Tom Lane | 2005-05-13 16:42:44 | Re: PostgreSQL strugling during high load |