Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 3B3C9633FBD for ; Wed, 3 Mar 2010 14:33:27 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 60405-09-2 for ; Wed, 3 Mar 2010 18:33:14 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mail.postgresql.org (Postfix) with ESMTP id 3FBC5633CE3 for ; Wed, 3 Mar 2010 14:32:51 -0400 (AST) Received: by ewy26 with SMTP id 26so1178087ewy.3 for ; Wed, 03 Mar 2010 10:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0RnifRyxnDZxfRcaytN6pcB1ffejDKE/fcG9e3QVJuc=; b=S8G3sFaxi+UUYhor6wv4MN3ysjbo6Q3MXAEUbFLhBLNP+EmCKhHvaGACADFJRUXOaT 6lJBvGtzut+WlcUfk/8a8P+6RorGYbPOcPoloft5JbCSs5wPGuMlxeSVd7eJcVQljE3W /4SCWy2NC4hz4R3vjZx/C1LBaERGuXIKkLQmU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gVh0RkoQsNFqSp4bzmt1vxZJ9g52JMDDwcfTUohBGibqHmhqC5iF56ejEXDtF1eEH7 nAfL4QLIgszeGlTO0GGWozkU215xWevHSrip8VMpijJApEILbY0r8U8yZpy9UWxnShEu bsocD0vm4+pcWfpQvPTExaNiJhzuNmXUV/z8Q= MIME-Version: 1.0 Received: by 10.216.167.131 with SMTP id i3mr1010004wel.94.1267641170660; Wed, 03 Mar 2010 10:32:50 -0800 (PST) In-Reply-To: <1267617205.5157.12.camel@hvost> References: <4B8D7A6C.3010304@gmail.com> <4B8E2EC1.2040100@gmail.com> <1267617205.5157.12.camel@hvost> Date: Wed, 3 Mar 2010 11:32:50 -0700 Message-ID: Subject: Re: 10K vs 15k rpm for analytics From: Scott Marlowe To: Hannu Krosing Cc: Yeb Havinga , Francisco Reyes , Pgsql performance Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.268 tagged_above=-10 required=5 tests=AWL=-1.083, BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201003/63 X-Sequence-Number: 37888 On Wed, Mar 3, 2010 at 4:53 AM, Hannu Krosing wrote: > On Wed, 2010-03-03 at 10:41 +0100, Yeb Havinga wrote: >> Scott Marlowe wrote: >> > On Tue, Mar 2, 2010 at 1:51 PM, Yeb Havinga wro= te: >> > >> >> With 24 drives it'll probably be the controller that is the limiting = factor >> >> of bandwidth. Our HP SAN controller with 28 15K drives delivers 170MB= /s at >> >> maximum with raid 0 and about 155MB/s with raid 1+0. So I'd go for th= e 10K >> >> drives and put the saved money towards the controller (or maybe more = than >> >> one controller). >> >> >> > >> > That's horrifically bad numbers for that many drives. =A0I can get tho= se >> > numbers for write performance on a RAID-6 on our office server. =A0I >> > wonder what's making your SAN setup so slow? >> > >> Pre scriptum: >> A few minutes ago I mailed detailed information in the same thread but >> as reply to an earlier response - it tells more about setup and gives >> results of a raid1+0 test. >> >> I just have to react to "horrifically bad" and "slow" :-) : The HP san >> can do raid5 on 28 disks also on about 155MBps: > > SAN-s are "horrifically bad" and "slow" mainly because of the 2MBit sec > fiber channel. > But older ones may be just slow internally as well. > The fact that it is expensive does not make it fast. > If you need fast thrughput, use direct attached storage Let me be clear that the only number mentioned at the beginning was throughput. If you're designing a machine to run huge queries and return huge amounts of data that matters. OLAP. If you're designing for OLTP you're likely to only have a few megs a second passing through but in thousands of xactions per second. So, when presented with the only metric of throughput, I figured that's what the OP was designing for. For OLTP his SAN is plenty fast.