From: Ian Westmacott <ianw@intellivid.com>
To: Jim C. Nasby <decibel@decibel.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: VACUUM and read-mostly tables
Date: Tue, 05 Apr 2005 11:13:06 -0400
Message-ID: <1112713986.8115.81.camel@spectre.intellivid.com> (raw)
In-Reply-To: <20050405044128.GL93835@decibel.org>
References: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net>
<20050405044128.GL93835@decibel.org>
On Tue, 2005-04-05 at 00:41, Jim C. Nasby wrote:
> We'll only answer if you do a write-up on your database. :P
>
> Seriously, those are some seriously big numbers. What else is the
> database doing? What hardware is it running on?
We run on a dual 3.2GHz P4 with 2GB RAM, but are still
finalizing the storage hardware. We've tried various
flavors of RAID, filesystems and volume management (and
are anxious to try out tablespaces in 8). We've found
fragmentation to be our largest limiting factor. XFS
helps with that, and seems to provide the highest
sustained throughput on raw tables, but its not the end
of the story since fragmentation is still high.
--Ian
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: ianw@intellivid.com, decibel@decibel.org
Subject: Re: VACUUM and read-mostly tables
In-Reply-To: <1112713986.8115.81.camel@spectre.intellivid.com>
References: <000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net> <20050405044128.GL93835@decibel.org> <1112713986.8115.81.camel@spectre.intellivid.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