X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1F64AD1B20B; Fri, 14 May 2004 07:15:30 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 71203-04; Fri, 14 May 2004 07:15:11 -0300 (ADT) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [202.0.58.20]) by svr1.postgresql.org (Postfix) with ESMTP id A874FD1B19F; Fri, 14 May 2004 07:15:07 -0300 (ADT) Received: from smtp-2.paradise.net.nz (smtp-2b.paradise.net.nz [202.0.32.211]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HXP00EWZ8H80F@linda-1.paradise.net.nz>; Fri, 14 May 2004 22:15:09 +1200 (NZST) Received: from paradise.net.nz (203-79-100-84.adsl.paradise.net.nz [203.79.100.84]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id D9A6F9E248; Fri, 14 May 2004 22:15:07 +1200 (NZST) Date: Fri, 14 May 2004 22:17:10 +1200 From: Mark Kirkwood Subject: Re: [PERFORM] Quad processor options - summary In-reply-to: <40A3EE5B.1050104@turtle-entertainment.de> To: Bjoern Metzdorf Cc: James Thornton , pgsql-performance@postgresql.org, pgsql-admin@postgresql.org Message-id: <40A49CA6.1020500@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040404 References: <40A2A7FA.6060403@turtle-entertainment.de> <40A3E250.2020204@jamesthornton.com> <40A3EE5B.1050104@turtle-entertainment.de> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200405/142 X-Sequence-Number: 13458 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. > >