Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 06FBC650138 for ; Thu, 28 Aug 2008 18:47:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 23340-02 for ; Thu, 28 Aug 2008 18:47:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by postgresql.org (Postfix) with ESMTP id 325AB6500A4 for ; Thu, 28 Aug 2008 18:47:39 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so747986rvf.43 for ; Thu, 28 Aug 2008 14:47:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=r4j3EgmLdkpxQjWA3lP2yFahJLRe0zCjFqeqh5jXo+8=; b=AG7wLfsi59nUiXItMAv6ZCwioyuwuMjgjbk48kDGBevfg8KhGdNie15YnOtyvuwFCc OiROpMNR+OtNMWtRuE+pzH8k+v2DMXJDK+hEypLQilaFWWboRvy5UVQpkRn9vYMZsAKx 2bUcS5Bja7qmN2pjnS9+CL/rFZeQJ+IMoajoo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Wxw+CNGMzvOk119cNswlNpGVz92O1LI55NjxtA8QQzCdBwS/tPrE2THD5UOG5ZUcUQ AowQAgjbNv9m62+nDi3dzhWotxQLkjaPIFJ2vktY505/DdwgbvcI4070koknmH9XwKQo gMOacnJ42YtFVCNiH20M3f3ylqBGcpAeiCrbM= Received: by 10.141.83.15 with SMTP id k15mr1035477rvl.289.1219960057586; Thu, 28 Aug 2008 14:47:37 -0700 (PDT) Received: by 10.141.197.1 with HTTP; Thu, 28 Aug 2008 14:47:37 -0700 (PDT) Message-ID: Date: Thu, 28 Aug 2008 15:47:37 -0600 From: "Scott Marlowe" To: "Fernando Hevia" Subject: Re: Best hardware/cost tradoff? Cc: cluster , pgsql-performance@postgresql.org In-Reply-To: <064701c90949$51d117d0$8f01010a@iptel.com.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <064701c90949$51d117d0$8f01010a@iptel.com.ar> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/393 X-Sequence-Number: 31274 On Thu, Aug 28, 2008 at 2:04 PM, Fernando Hevia wrote: > > I havent had any issues with software raid (mdadm) and hot-swaps. It keeps > working in degraded mode and as soon as you replace the defective disk it > can reconstruct the array on the fly. Performance will suffer while at it > but the service keeps up. I too put my vote behind mdadm for ease of use. However, there are reports that certain levels of RAID in linux kernel RAID that are supposed to NOT handle write barriers properly. So that's what worries me. > The battery backup makes a very strong point for a hw controller. Still, I > have heard good things on combining a HW controller with JBODS leaving the > RAID affair to mdadm. In your scenario though with "*lots* of random reads", This is especially true on slower RAID controllers. A lot of RAID controllers in the $300 range with battery backed caching don't do RAID real well, but do caching ok. If you can't afford a $1200 RAID card then this might be a good option.