From: Matt Clark <matt@ymogen.net>
To: 'Dawid Kuroczko' <qnex42@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: ext3 journalling type
Date: Mon, 8 Nov 2004 15:14:04 -0000
Message-ID: <000d01c4c5a5$96202020$8300a8c0@solent> (raw)
In-Reply-To: <758d5e7f04110804263efdf475@mail.gmail.com>
> Am I right to assume that "writeback" is both fastest and at
> the same time as safe to use as ordered? Maybe any of you
> did some benchmarks?
It should be fastest because it is the least overhead, and safe because
postgres does it's own write-order guaranteeing through fsync(). You should
also mount the FS with the 'noatime' option.
But.... For some workloads, there are tests showing that 'data=journal' can
be the fastest! This is because although the data is written twice (once to
the journal, and then to its real location on disk) in this mode data is
written _sequentially_ to the journal, and later written out to its
destination, which may be at a quieter time.
There's a discussion (based around 7.2) here:
http://www.kerneltraffic.org/kernel-traffic/kt20020401_160.txt
M
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: matt@ymogen.net, qnex42@gmail.com
Subject: Re: ext3 journalling type
In-Reply-To: <000d01c4c5a5$96202020$8300a8c0@solent>
* 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