From: | "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com> |
---|---|
To: | <jao(at)geophile(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Trying to minimize the impact of checkpoints (resend) |
Date: | 2004-06-12 00:18:41 |
Message-ID: | 71E37EF6B7DCC1499CEA0316A256832801057AEE@loki.wc.globexplorer.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
There is something wonky on this mail list. I did not send this.
-----Original Message-----
From: Gregory S. Williamson
Sent: Fri 6/11/2004 2:10 PM
To: jao(at)geophile(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Trying to minimize the impact of checkpoints (resend)
In-reply-to: <1086983714(dot)40ca0e22a9cb4(at)geophile(dot)com>
References: <1086983714(dot)40ca0e22a9cb4(at)geophile(dot)com>
Comments: In-reply-to jao(at)geophile(dot)commessage dated "Fri, 11 Jun 2004
15:55:14 -0400"
Date: Fri, 11 Jun 2004 16:42:19 -0400
Message-ID: <18295(dot)1086986539(at)sss(dot)pgh(dot)pa(dot)us>
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level:
X-Mailing-List: pgsql-general
Precedence: bulk
Sender: pgsql-general-owner(at)postgresql(dot)org
X-imss-version: 2.5
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:15 M:2 S:5 R:5
X-imss-settings: Baseline:2 C:2 M:2 S:2 R:2 (0.1500 0.1500)
Return-Path: pgsql-general-owner+M61832(at)postgresql(dot)org
X-OriginalArrivalTime: 11 Jun 2004 20:51:04.0152 (UTC) FILETIME=[CF961D80:01C44FF5]
jao(at)geophile(dot)com writes:
> I'm using PostgreSQL 7.3.4 on RH9. Data and logs are on separate
> disks. (These are low-end IDE disks. That part of the problem
> is out of my control.)
> When a checkpoint occurs, all operations slow way, way down.
Not too surprising; you haven't got enough I/O bandwidth.
> Does anyone have any experience in modifying the priority of the
> checkpoint process itself, (re-nicing it)?
That would be a waste of time, because your problem is with I/O usage
not CPU usage, and nice doesn't impact I/O scheduling AFAIK.
You might be able to get somewhere by inserting intrapage delays into
the checkpoint write loop, similar to what's been done to VACUUM since
7.4. (I have a todo item to do this for CVS tip, in fact.) You'd not
want this to happen during a shutdown checkpoint, but for ordinary
checkpoints I don't believe there's any problem with spacing out the
writes.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-06-12 04:39:18 | Release 7.4.3 branded |
Previous Message | Steve Wolfe | 2004-06-11 22:53:00 | Re: Opteron scaling with PostgreSQL |