From: Mark Kirkwood <markir@paradise.net.nz>
To: Bjoern Metzdorf <bm@turtle-entertainment.de>
Cc: James Thornton <james@jamesthornton.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [PERFORM] Quad processor options - summary
Date: Fri, 14 May 2004 22:17:10 +1200
Message-ID: <40A49CA6.1020500@paradise.net.nz> (raw)
In-Reply-To: <40A3EE5B.1050104@turtle-entertainment.de>
References: <Pine.LNX.4.33.0405120741190.25767-100000@css120.ihs.com>
<40A2A7FA.6060403@turtle-entertainment.de>
<40A3E250.2020204@jamesthornton.com>
<40A3EE5B.1050104@turtle-entertainment.de>
I would recommend trying out several stripe sizes, and making your own
measurements.
A while ago I was involved in building a data warehouse system (Oracle,
DB2) and after several file and db benchmark exercises we used 256K
stripes, as these gave the best overall performance results for both
systems.
I am not saying "1M is wrong", but I am saying "1M may not be right" :-)
regards
Mark
Bjoern Metzdorf wrote:
>
> 1. Get many drives and stripe them into a RAID0 with a stripe width of
> 1MB. I am not quite sure if this stripe width is to be controlled at
> the application level (does postgres support this?) or if e.g. the
> "chunk size" of the linux software driver is meant. Normally a chunk
> size of 4KB is recommended, so 1MB sounds fairly large.
>
>
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: markir@paradise.net.nz, bm@turtle-entertainment.de, james@jamesthornton.com, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] Quad processor options - summary
In-Reply-To: <40A49CA6.1020500@paradise.net.nz>
* 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