From: Josh Berkus <josh@agliodbs.com>
To: Andreas Pflug <Andreas.Pflug@web.de>
To: pgsql-performance@postgresql.org
Subject: Re: how to configure my new server
Date: Fri, 7 Feb 2003 09:16:27 -0800
Message-ID: <200302070916.27541.josh@agliodbs.com> (raw)
In-Reply-To: <3E4326B6.5030100@web.de>
References: <web-2828247@davinci.ethosmedia.com>
<3E4326B6.5030100@web.de>
Andreas,
> Josh wrote:
> >> With a large database you may even think about
> >> shifting individual tables or indexes to seperate disks.
>
> OK, I admit it was a bit provoking. It was my intention to stir things up a
> little bit ;-) IMHO, thinking about locating data on dedicated files is a
> waste of time on small servers. Let the hardware do the job for you! It is
> "good enough".
Aha, by "large databases" I mean "several million records". In the odd case
where you have a database which has one or two tables which are larger than
the rest of the database combined, you can get a performance boost by putting
those tables, and/or their indexes, on a seperate spindle.
Frankly, for small servers, a pair of mirrored IDE drives is adequate. And,
of course, if you have a RAID 1+0 controller, that's better than trying to
directly allocate different files to different disks ... except the WAL log.
> I don't think solid state disks are a way out (unless you don't know where
> to bury your money :-). Maybe the gurus can tell more about PostgreSQL's
> caching, but for my opinion if enough RAM is available after some time all
> of the DB should be in cache eliminating the need to access the disks for
> read access. For writing, which is typically less than 10 % of total load,
> an optimizing caching disk controller should be sufficient.
Depends on the database. I've worked on DBs where writes were 40% of all
queries ... and 90% of the system resource load. For those databases,
moving the WAL log to a RAMdisk might mean a big boost.
Also, I'm currently working to figure out a solution for some 1U machines
which don't have any *room* for an extra drive for WAL. A PCI ramdisk would
be just perfect ...
--
Josh Berkus
Aglio Database Solutions
San Francisco
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-performance@postgresql.org
Cc: josh@agliodbs.com, Andreas.Pflug@web.de
Subject: Re: how to configure my new server
In-Reply-To: <200302070916.27541.josh@agliodbs.com>
References: <web-2828247@davinci.ethosmedia.com> <3E4326B6.5030100@web.de> <200302070916.27541.josh@agliodbs.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