From: Laurent Laborde <kerdezixe@gmail.com>
To: Ivan Voras <ivoras@freebsd.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: limiting performance impact of wal archiving.
Date: Tue, 10 Nov 2009 16:29:32 +0100
Message-ID: <8a1bfe660911100729q42ac732cga9bbadd52e2533dd@mail.gmail.com> (raw)
In-Reply-To: <hdbvqt$7v8$1@ger.gmane.org>
References: <8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com>
<hdbrv8$p35$1@ger.gmane.org>
<8a1bfe660911100700l2a44f638m97ea6136b65deb21@mail.gmail.com>
<hdbvqt$7v8$1@ger.gmane.org>
On Tue, Nov 10, 2009 at 4:11 PM, Ivan Voras <ivoras@freebsd.org> wrote:
> Laurent Laborde wrote:
>
> Ok, this explains it. It also means you are probably not getting much
> runtime performance benefits from the logging and should think about moving
> the logs to different drive(s), among other things because...
It is on a separate array which does everything but tablespace (on a
separate array) and indexspace (another separate array).
>> Of course, when doing sequential read it goes to +250MB/s :)
>
> ... it means you cannot dedicate 0.064 of second from the array to read
> through a single log file without your other transactions suffering.
Well, actually, i also change the configuration to synchronous_commit=off
It probably was *THE* problem with checkpoint and archiving :)
But adding cstream couldn't hurt performance, and i wanted to share
this with the list. :)
BTW, if you have any idea to improve IO performance, i'll happily read it.
We're 100% IO bound.
eg: historically, we use JFS with LVM on linux. from the good old time
when IO wasn't a problem.
i heard that ext3 is not better for postgresql. what else ? xfs ?
*hugs*
--
ker2x
Sysadmin & DBA @ http://www.over-blog.com/
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: kerdezixe@gmail.com, ivoras@freebsd.org
Subject: Re: limiting performance impact of wal archiving.
In-Reply-To: <8a1bfe660911100729q42ac732cga9bbadd52e2533dd@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