pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Mindaugas Riauba <mind@bi.lt>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL strugling during high load
Date: Sun, 15 May 2005 22:26:50 -0400
Message-ID: <428804EA.6080609@zeut.net> (raw)
In-Reply-To: <022901c557c5$73df1220$f20214ac@bite.lt>
References: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt>
<23217.1115991763@sss.pgh.pa.us>
<022901c557c5$73df1220$f20214ac@bite.lt>
Mindaugas Riauba wrote:
>>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.
>>
>>
>
> It looks like that not only vacuum causes our problems. vacuum_cost
>seems to lower vacuum impact but we are still noticing slow queries "storm".
>We are logging queries that takes >2000ms to process.
> And there is quiet periods and then suddenly 30+ slow queries appears in
>log within the same second. What else could cause such behaviour? WAL log
>switch? One WAL file seems to last <1 minute.
>
>
How long are these quite periods? Do the "strom" periods correspond to
pg_autovacuum loops? I have heard from one person who had LOTS of
databases and tables that caused the pg_autovacuum to create a noticable
load just updateing all its stats. The solution in that case was to add
a small delay insidet the inner pg_autovacuum loop.
view thread (21+ messages) latest in thread
Message-ID: <428804EA.6080609@zeut.net> Permalink: ../428804EA.6080609@zeut.net/ Also on: postgresql.org/message-id/428804EA.6080609@zeut.net ·
reply
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: matthew@zeut.net, mind@bi.lt, tgl@sss.pgh.pa.us Subject: Re: PostgreSQL strugling during high load In-Reply-To: <428804EA.6080609@zeut.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