From: Bill Moran <wmoran@collaborativefusion.com>
To: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-performance@postgresql.org
Subject: Re: autovacuum on a -mostly- r/o table
Date: Wed, 27 Sep 2006 16:27:56 -0400
Message-ID: <20060927162756.0a9df264.wmoran@collaborativefusion.com> (raw)
References: <451AA1FE.9050704@axa.it>
<1159374712.46586.47.camel@home>
In response to Edoardo Ceccarelli <eddy@axa.it>:
> Rod Taylor wrote:
> > On Wed, 2006-09-27 at 18:08 +0200, Edoardo Ceccarelli wrote:
> >
> >> I have read that autovacuum cannot check to see pg load before
> >> launching
> >> vacuum but is there any patch about it? that would sort out the
> >> problem
> >> in a good and simple way.
> >>
> >
> > In some cases the solution to high load is to vacuum the tables being
> > hit the heaviest -- meaning that simply checking machine load isn't
> > enough to make that decision.
> >
> > In fact, that high load problem is exactly why autovacuum was created in
> > the first place.
> >
> True,
> but autovacuum could check load -before- and -during- it's execution and
> it could adjust himself automatically to perform more or less
> aggressively depending on the difference between those two values.
> Maybe with a parameter like: maximum-autovacuum-load=0.2
> that would mean: "never load the machine more than 20% for the autovacuum"
This is pretty non-trivial. How do you define 20% load? 20% of the
CPU? Does that mean that it's OK for autovac to use 3% cpu and 100% of
your IO? Ok, so we need to calculate an average of IO and CPU -- which
disks? If your WAL logs are on one disk, and you've used tablespaces
to spread the rest of your DB across different partitions, it can
be pretty difficult to determine which IO parameters you want to take
into consideration.
--
Bill Moran
Collaborative Fusion Inc.
****************************************************************
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************
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: wmoran@collaborativefusion.com, eddy@axa.it
Subject: Re: autovacuum on a -mostly- r/o table
In-Reply-To: <20060927162756.0a9df264.wmoran@collaborativefusion.com>
* 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