pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew Nuzum <mattnuzum@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Thu, 14 Apr 2005 10:51:46 -0500
Message-ID: <f3c0b40805041408517d7ede90@mail.gmail.com> (raw)
In-Reply-To: <446.1113489854@sss.pgh.pa.us>
References: <d30377$1jn8$1@news.hub.org>
	<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>

On 4/14/05, Tom Lane <tgl@sss.pgh.pa.us> 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).  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...)
> 
> 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.
>   
> 

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?

-- 
Matthew Nuzum
www.bearfruit.org



view thread (119+ messages)  latest in thread

Message-ID: <f3c0b40805041408517d7ede90@mail.gmail.com>
Permalink:  ../f3c0b40805041408517d7ede90@mail.gmail.com/
Also on:    postgresql.org/message-id/f3c0b40805041408517d7ede90@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mattnuzum@gmail.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <f3c0b40805041408517d7ede90@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox