pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mindaugas Riauba <mind@bi.lt>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL strugling during high load
Date: Fri, 13 May 2005 17:10:01 +0300
Message-ID: <022901c557c5$73df1220$f20214ac@bite.lt> (raw)
References: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt>
	<23217.1115991763@sss.pgh.pa.us>


> > ... 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.

  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.

  And also in slow queries log only function call is shown. Maybe it is
possible
to get exact query which slows everything down in the serverlog?

  Thanks,

  Mindaugas




view thread (21+ messages)  latest in thread

Message-ID: <022901c557c5$73df1220$f20214ac@bite.lt>
Permalink:  ../022901c557c5$73df1220$f20214ac@bite.lt/
Also on:    postgresql.org/message-id/022901c557c5$73df1220$f20214ac@bite.lt

 · 

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: mind@bi.lt, tgl@sss.pgh.pa.us
  Subject: Re: PostgreSQL strugling during high load
  In-Reply-To: <022901c557c5$73df1220$f20214ac@bite.lt>

* 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