From: Scott Marlowe <scott.marlowe@gmail.com>
To: Campbell, Lance <lance@uiuc.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Backup causing poor performance - suggestions
Date: Mon, 5 May 2008 11:05:03 -0600
Message-ID: <dcc563d10805051005w568294efkc351c1390a227f1a@mail.gmail.com> (raw)
In-Reply-To: <B10E6810AC2A2F4EA7550D072CDE8760CDDD30@SAB-FENWICK.sab.uiuc.edu>
References: <B10E6810AC2A2F4EA7550D072CDE8760CDDD2C@SAB-FENWICK.sab.uiuc.edu>
<dcc563d10805050805t197e9c02ue1a5b09144c6a8f7@mail.gmail.com>
<B10E6810AC2A2F4EA7550D072CDE8760CDDD2D@SAB-FENWICK.sab.uiuc.edu>
<dcc563d10805050854k676d1288kc637612b02426b3d@mail.gmail.com>
<B10E6810AC2A2F4EA7550D072CDE8760CDDD30@SAB-FENWICK.sab.uiuc.edu>
On Mon, May 5, 2008 at 10:11 AM, Campbell, Lance <lance@uiuc.edu> wrote:
> Scott,
> The last 6 entries are when the system is not backing up. The system
> was running fine. But the other entries are when it was backing up.
> Reads seem to be fine but any operations that need to write data just
> hang.
Could you repost that as an attachment? the wrapping applied by your
email client makes it very hard to read.
Just perusing it, it doesn't look like you're CPU bound, but I/O bound.
As Craig mentioned, you may do better with some form of replication
solution here than pg_dumps.
Given that your db can fit in memory (when you say it's 8G do you mean
ON DISK, or in a backup? Big diff) then the only thing the backups
should be slowing down are update queries. Select queries shouldn't
even notice.
However, there's a LOT of wait state, and only blocks out, not really
many in, so I'm guessing that you've got a fair bit of writing going
on at the same time as your backups.
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: scott.marlowe@gmail.com, lance@uiuc.edu
Subject: Re: Backup causing poor performance - suggestions
In-Reply-To: <dcc563d10805051005w568294efkc351c1390a227f1a@mail.gmail.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