From: Gregory Stark <stark@enterprisedb.com>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Postgresql list Performance <pgsql-performance@postgresql.org>
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
Date: Thu, 26 Apr 2007 17:47:29 +0100
Message-ID: <87wszz6q1q.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <4630D4B6.9040802@modgraph-usa.com>
References: <3BD44C5D-E402-43EB-8FFD-1A4BC97AFD0C@decibel.org>
<20070426080050.522ef7b5.wmoran@collaborativefusion.com>
<463096AD.4020707@enterprisedb.com>
<20070426091432.274977fe.wmoran@collaborativefusion.com>
<4630D4B6.9040802@modgraph-usa.com>
"Craig A. James" <cjames@modgraph-usa.com> writes:
> More specifically, this problem was solved on UNIX file systems way back in the
> 1970's and 1980's. No UNIX file system (including Linux) since then has had
> significant fragmentation problems, unless the file system gets close to 100%
> full. If you run below 90% full, fragmentation shouldn't ever be a significant
> performance problem.
Note that the main technique used to avoid fragmentation -- paradoxically --
is to break the file up into reasonable sized chunks. This allows the
filesystem the flexibility to place the chunks efficiently.
In the case of a performance-critical file like the WAL that's always read
sequentially it may be to our advantage to defeat this technique and force it
to be allocated sequentially. I'm not sure whether any filesystems provide any
option to do so.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.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: stark@enterprisedb.com, cjames@modgraph-usa.com, wmoran@collaborativefusion.com, heikki@enterprisedb.com
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
In-Reply-To: <87wszz6q1q.fsf@oxford.xeocode.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