Re: limiting performance impact of wal archiving.

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Ivan Voras" <ivoras(at)freebsd(dot)org>, "Laurent Laborde" <kerdezixe(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: limiting performance impact of wal archiving.
Date: 2009-11-10 15:48:35
Message-ID: 4AF936F3020000250002C4F7@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Laurent Laborde <kerdezixe(at)gmail(dot)com> wrote:

> BTW, if you have any idea to improve IO performance, i'll happily
> read it. We're 100% IO bound.

At the risk of stating the obvious, you want to make sure you have
high quality RAID adapters with large battery backed cache configured
to write-back.

If you haven't already done so, you might want to try
elevator=deadline.

> xfs ?

If you use xfs and have the aforementioned BBU cache, be sure to turn
write barriers off.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Laurent Laborde 2009-11-10 15:53:49 Re: limiting performance impact of wal archiving.
Previous Message Scott Marlowe 2009-11-10 15:43:34 Re: limiting performance impact of wal archiving.