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 234DB535FA for ; Thu, 14 Apr 2005 12:55:52 -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 20825-06 for ; Thu, 14 Apr 2005 15:55:49 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by svr1.postgresql.org (Postfix) with ESMTP id 384255294A for ; Thu, 14 Apr 2005 12:55:48 -0300 (ADT) Received: by rproxy.gmail.com with SMTP id a41so423946rng for ; Thu, 14 Apr 2005 08:55:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:reply-to:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:x-mimeole:message-id; b=Lp71ryPPqozICeY/5xxDMeTIfw8J2m5+toI1SaAW+FpvfT0ewdP9nT74VwuqW0/way3neNbEYGenzhe8CnGiFCaZH5jNqcDGuBjAqN45EpLQuA8DbcDfJNq8yLYOdSaJXFNwuTvupHTTaWdX8iMQeequsEziifDqbD+PL61BnQk= Received: by 10.38.86.53 with SMTP id j53mr1985130rnb; Thu, 14 Apr 2005 08:55:47 -0700 (PDT) Received: from MATTSPC ([12.216.69.41]) by mx.gmail.com with ESMTP id 79sm718502rna.2005.04.14.08.55.47; Thu, 14 Apr 2005 08:55:47 -0700 (PDT) Reply-To: From: "Matthew Nuzum" To: Subject: Re: How to improve db performance with $7K? Date: Thu, 14 Apr 2005 10:55:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcVBCmlHOghtl6diTSCMaQNVQ5qOzg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: <425e9283.0422c9db.394e.ffffb643@mx.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.304 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/293 X-Sequence-Number: 11690 On 4/14/05, Tom Lane wrote: > > 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). =A0Also, in SCSI = it's > possible for the drive to rearrange reads as well as writes --- which > AFAICS is just not possible in ATA. =A0(Maybe in the newest spec...) > > 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. =A0Variable-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. =A0Combine 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. > > 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.followers.net - Makers of =93Elite Content Management System=94 View samples of Elite CMS in action by visiting http://www.followers.net/portfolio/