From: Bill Moran <wmoran@collaborativefusion.com>
To: George Pavlov <gpavlov@mynewplace.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PITR performance overhead?
Date: Tue, 1 Aug 2006 12:59:00 -0400
Message-ID: <20060801125900.30430a9f.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <8C5B026B51B6854CBE88121DBF097A863329F2@ehost010-33.exch010.intermedia.net>
References: <20060731170833.GH2900@mathom.us>
<8C5B026B51B6854CBE88121DBF097A863329F2@ehost010-33.exch010.intermedia.net>
In response to "George Pavlov" <gpavlov@mynewplace.com>:
> I am looking for some general guidelines on what is the performance
> overhead of enabling point-in-time recovery (archive_command config) on
> an 8.1 database. Obviously it will depend on a multitude of factors, but
> some broad-brush statements and/or anecdotal evidence will suffice.
> Should one worry about its performance implications? Also, what can one
> do to mitigate it?
Prior to implementing PITR, I did some testing to see what kind of
overhead it would add. It was negligible. I don't remember the details,
but I seem to remember the performance hit was barely measurable.
Note that in our usage scenarios, we have very little IO compared to
CPU usage. The result is that our DB servers have plenty of disk
bandwidth to spare. Since the log backup occurs as a background
process, it made almost no difference in our tests. If your DB is
very IO intensive, you may have different results.
--
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, gpavlov@mynewplace.com
Subject: Re: PITR performance overhead?
In-Reply-To: <20060801125900.30430a9f.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