X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 18C8453B94 for ; Thu, 14 Apr 2005 12:52:06 -0300 (ADT) 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 20249-03 for ; Thu, 14 Apr 2005 15:51:53 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by svr1.postgresql.org (Postfix) with ESMTP id 79AC853BA5 for ; Thu, 14 Apr 2005 12:51:51 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so510409wri for ; Thu, 14 Apr 2005 08:51:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Svr5F4Hts73xnWkRk04ZyFduZm4eQ95jITJPrLZ1nrzZ62unsku0thCiDdv6RkVxr5JBmh1CVHLl/c1Ipyd+RCcd7QSUCrqO81fA9daIWHK1VIyzCXW4b7G6MTItPuXWX1KMVSdJL3K/burm+U5l3PiDjp7Xes88kCSPInqj8Ig= Received: by 10.54.68.9 with SMTP id q9mr846587wra; Thu, 14 Apr 2005 08:51:47 -0700 (PDT) Received: by 10.54.22.6 with HTTP; Thu, 14 Apr 2005 08:51:46 -0700 (PDT) Message-ID: Date: Thu, 14 Apr 2005 10:51:46 -0500 From: Matthew Nuzum Reply-To: newz@bearfruit.org To: pgsql-performance@postgresql.org Subject: Re: How to improve db performance with $7K? In-Reply-To: <446.1113489854@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <33c6269f050406151241b01148@mail.gmail.com> <20050406224102.GM93835@decibel.org> <33c6269f0504061732195f6ae4@mail.gmail.com> <87wtrfmgt5.fsf@stark.xeocode.com> <13449.1112847297@sss.pgh.pa.us> <20050414055655.GB19518@filer> <878y3lj23o.fsf@stark.xeocode.com> <20050414083608.GC19518@filer> <446.1113489854@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.398 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/442 X-Sequence-Number: 11839 On 4/14/05, Tom Lane wrote: >=20 > That's basically what it comes down to: SCSI lets the disk drive itself > do the low-level I/O scheduling whereas the ATA spec prevents the drive > from doing so (unless it cheats, ie, caches writes). Also, in SCSI it's > possible for the drive to rearrange reads as well as writes --- which > AFAICS is just not possible in ATA. (Maybe in the newest spec...) >=20 > The reason this is so much more of a win than it was when ATA was > designed is that in modern drives the kernel has very little clue about > the physical geometry of the disk. Variable-size tracks, bad-block > sparing, and stuff like that make for a very hard-to-predict mapping > from linear sector addresses to actual disk locations. Combine that > with the fact that the drive controller can be much smarter than it was > twenty years ago, and you can see that the case for doing I/O scheduling > in the kernel and not in the drive is pretty weak. > =20 >=20 So if you all were going to choose between two hard drives where: drive A has capacity C and spins at 15K rpms, and drive B has capacity 2 x C and spins at 10K rpms and all other features are the same, the price is the same and C is enough disk space which would you choose? I've noticed that on IDE drives, as the capacity increases the data density increases and there is a pereceived (I've not measured it) performance increase. Would the increased data density of the higher capacity drive be of greater benefit than the faster spindle speed of drive A? --=20 Matthew Nuzum www.bearfruit.org