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

Re: [PERFORM] Quad processor options - summary

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Bjoern Metzdorf <bm(at)turtle-entertainment(dot)de>
Cc: James Thornton <james(at)jamesthornton(dot)com>,pgsql-performance(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [PERFORM] Quad processor options - summary
Date: 2004-05-14 10:17:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-performance
I would recommend trying out several stripe sizes, and making your own 

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 

I am not saying "1M is wrong", but I am saying "1M may not be right" :-)



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.

In response to

pgsql-performance by date

Next:From: Fabio PanizzuttiDate: 2004-05-14 10:30:16
Subject: R: R: R: Query plan on identical tables differs . Why ?
Previous:From: Christopher Kings-LynneDate: 2004-05-14 09:55:17
Subject: Re: R: R: Query plan on identical tables differs . Why ?

pgsql-admin by date

Next:From: Jørgen Lie PettersenDate: 2004-05-14 13:12:15
Subject: Query
Previous:From: Laurens WagemakersDate: 2004-05-14 09:41:30
Subject: Re: GNUmakefile size 0

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