From: Michael Stone <mstone+postgres@mathom.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgresql Performance on an HP DL385 and
Date: Tue, 15 Aug 2006 13:25:21 -0400
Message-ID: <20060815172519.GT2900@mathom.us> (raw)
In-Reply-To: <20060815162524.GR27928@pervasive.com>
References: <3E37B936B592014B978C4415F90D662D03FFEF6E@MI8NYCMAIL06.Mi8.com>
<721b21dc0608082245u6ee62e7dg522ff18e4d72683@mail.gmail.com>
<20060809210539.GR40481@pervasive.com>
<1155180553.13315.0.camel@amd64-gentoo-laptop>
<20060810110935.GF2900@mathom.us>
<20060814153841.GF27928@pervasive.com>
<20060814170338.GM2900@mathom.us>
<20060815162524.GR27928@pervasive.com>
On Tue, Aug 15, 2006 at 11:25:24AM -0500, Jim C. Nasby wrote:
>Well, if the controller is caching with a BBU, I'm not sure that order
>matters anymore, because the controller should be able to re-order at
>will. Theoretically. :) But this is why having some actual data posted
>somewhere would be great.
You're missing the point. It's not a question of what happens once it
gets to the disk/controller, it's a question of whether the xlog write
has to compete with some other write activity before the write gets to
the disk (e.g., at the filesystem level). If you've got a bunch of stuff
in a write buffer on the OS level and you try to push the xlog write
out, you may have to wait for the other stuff to get to the controller
write cache before the xlog does. It doesn't matter if you don't have to
wait for the write to get from the controller cache to the disk if you
already had to wait to get to the controller cache. The effect is a
*lot* smaller than not having a non-volatile cache, but it is an
improvement. (Also, the difference between ext2 and xfs for the xlog is
pretty big itself, and a good reason all by itself to put xlog on a
seperate partition that's small enough to not need journalling.)
Mike Stone
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: mstone+postgres@mathom.us, jnasby@pervasive.com
Subject: Re: Postgresql Performance on an HP DL385 and
In-Reply-To: <20060815172519.GT2900@mathom.us>
* 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