From: Florian Weimer <fweimer@bfk.de>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Jim Nasby <decibel@decibel.org>
Cc: Postgresql list Performance <pgsql-performance@postgresql.org>
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
Date: Fri, 27 Apr 2007 09:39:28 +0200
Message-ID: <82d51q9sgf.fsf@mid.bfk.de> (raw)
In-Reply-To: <20070426091432.274977fe.wmoran@collaborativefusion.com>
References: <3BD44C5D-E402-43EB-8FFD-1A4BC97AFD0C@decibel.org>
<20070426080050.522ef7b5.wmoran@collaborativefusion.com>
<463096AD.4020707@enterprisedb.com>
<20070426091432.274977fe.wmoran@collaborativefusion.com>
* Bill Moran:
> To clarify my viewpoint:
> To my knowledge, there is no Unix filesystem that _suffers_ from
> fragmentation. Specifically, all filessytems have some degree of
> fragmentation that occurs, but every Unix filesystem that I am aware of
> has built-in mechanisms to mitigate this and prevent it from becoming
> a performance issue.
One database engine tends to create a huge number of fragments because
the files are written with holes in them. There is a significant
impact on sequential reads, but that doesn't matter much because the
engine doesn't implement fast, out-of-order B-tree scans anyway. 8-/
I still think that preallocating in reasonably sized chunks is
beneficial.
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
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: fweimer@bfk.de, wmoran@collaborativefusion.com, heikki@enterprisedb.com, decibel@decibel.org
Subject: Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
In-Reply-To: <82d51q9sgf.fsf@mid.bfk.de>
* 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