Skip site navigation (1) Skip section navigation (2)

Re: Filesystem fragmentation (Re: Fragmentation of WAL files)

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>
Cc: "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Postgresql list Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
Date: 2007-04-26 16:47:29
Message-ID: 87wszz6q1q.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-performance
"Craig A. James" <cjames(at)modgraph-usa(dot)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


In response to

Responses

pgsql-performance by date

Next:From: Leif B. KristensenDate: 2007-04-26 16:55:42
Subject: Re: Feature request - have postgresql log warning when new sub-release comes out.
Previous:From: Craig A. JamesDate: 2007-04-26 16:35:02
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group