X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3579ED8CA0 for ; Wed, 16 Nov 2005 16:09:22 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37656-10 for ; Wed, 16 Nov 2005 20:09:22 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 761ACD8B2D for ; Wed, 16 Nov 2005 16:09:19 -0400 (AST) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 16 Nov 2005 14:08:03 -0600 Subject: Re: Hardware/OS recommendations for large databases ( From: Scott Marlowe To: "Steinar H. Gunderson" Cc: pgsql-performance@postgresql.org In-Reply-To: <20051116185138.GA22831@uio.no> References: <3E37B936B592014B978C4415F90D662D01995F7B@MI8NYCMAIL06.Mi8.com> <33c6269f0511152115v1a34ab81j30f1f5df5a6c6956@mail.gmail.com> <437B3B18.1040509@commandprompt.com> <437B4773.1040404@boreham.org> <1132160785.3582.60.camel@state.g2switchworks.com> <20051116185138.GA22831@uio.no> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1132171683.3582.85.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 16 Nov 2005 14:08:03 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200511/297 X-Sequence-Number: 15554 On Wed, 2005-11-16 at 12:51, Steinar H. Gunderson wrote: > On Wed, Nov 16, 2005 at 11:06:25AM -0600, Scott Marlowe wrote: > > There was a big commercial EMC style array in the hosting center at the > > same place that had something like a 16 wide by 16 tall array of IDE > > drives for storing pdf / tiff stuff on it, and we had at least one > > failure a month in it. Of course, that's 256 drives, so you're gonna > > have failures, and it was configured with a spare on every other row or > > some such. We just had a big box of hard drives and it was smart enough > > to rebuild automagically when you put a new one in, so the maintenance > > wasn't really that bad. The performance was quite impressive too. > > If you have a cool SAN, it alerts you and removes all data off a disk > _before_ it starts giving hard failures :-) Yeah, I forget who made the unit we used, but it was pretty much fully automated. IT was something like a large RAID 5+0 (0+5???) and would send an alert when a drive died or started getting errors, and the bad drive's caddy would be flashing read instead of steady green. I just remember thinking that I'd never used a drive array that was taller than I was before that.