X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.225.181]) by svr1.postgresql.org (Postfix) with ESMTP id 62117D1C935 for ; Tue, 22 Jul 2003 16:13:16 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr5.postgresql.org [64.117.225.181]) (amavisd-new, port 10024) with ESMTP id 62032-02 for ; Tue, 22 Jul 2003 16:13:05 +0000 (GMT) Received: from lorax.kciLink.com (lorax.kciLink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id E6D85D1C4C8 for ; Tue, 22 Jul 2003 13:13:04 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kciLink.com (Postfix) with ESMTP id DF1F03E3B for ; Tue, 22 Jul 2003 12:13:04 -0400 (EDT) Received: from lorax.kciLink.com ([127.0.0.1]) by localhost (lorax.kciLink.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 68669-07 for ; Tue, 22 Jul 2003 12:12:54 -0400 (EDT) Received: by lorax.kciLink.com (Postfix, from userid 8) id 81E6C3E26; Tue, 22 Jul 2003 12:12:54 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: Tuning PostgreSQL Date: Tue, 22 Jul 2003 12:12:54 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 32 Message-ID: References: <9B1C77393DED0D4B9DAA1AA1742942DA3BCCB1@pos_pdc.posportal.com> <014a01c34f90$74bc2c80$b696a8c0@APR> <200307210906.10226.josh@agliodbs.com> <20030721162852.GN19009@md2.mediadesign.nl> <002901c3501f$86565940$b696a8c0@APR> <20030722094035.GU19009@md2.mediadesign.nl> <009901c35054$fad824d0$b696a8c0@APR> <20030722143335.GH55392@nasby.net> <00d301c35062$25c943b0$b696a8c0@APR> NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kciLink.com 1058890374 76195 216.194.193.105 (22 Jul 2003 16:12:54 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Tue, 22 Jul 2003 16:12:54 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Portable Code, berkeley-unix) Cancel-Lock: sha1:8aP6W9ol3HlIvl3jbYTzRQpKJZ4= X-Virus-Scanned: by amavisd-new at kciLink.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/359 X-Sequence-Number: 2652 >>>>> "AP" == Alexander Priem writes: AP> Hmmm. I keep changing my mind about this. My Db would be mostly AP> 'selecting', but there would also be pretty much inserting and AP> updating done. But most of the work would be selects. So would AP> this config be OK? I'm about to order a new server. I haven't decided exactly how many disks I will get, but my plan is to get an 8-disk RAID10 with 15k RPM drives. I don't need the volume, just the speed and number of spindles, so I'm buying the smallest drives that meet my speed probably 18Gb each (sheesh! I remember getting my first 5Mb disk for my 8088 PC in college and thinking that was too much space). My mix is nearly even read/write, but probably a little biased towards the reading. This machine is replacing a 5-disk box that was switched from RAID5 to 4-disk RAID10 for data plus one system disk in January (what a pain that was to re-index, but that's another story). The switch from RAID5 to RAID10 made an enormous improvement in performance. The speedup wasn't from recreating the database: It was restored from a file-level backup so the actual files were not compacted or secretly "improved" in any way, other than my occasional reindexing. So I think your 6-disk RAID10 will be good. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/