Re: 8x2.5" or 6x3.5" disks - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: 8x2.5" or 6x3.5" disks
Date
Msg-id dcc563d10801290700l5138d13fvb9fa05b66ddc32f2@mail.gmail.com
Whole thread Raw
In response to Re: 8x2.5" or 6x3.5" disks  ("Mike Smith" <mike.smith@enterprisedb.com>)
List pgsql-performance
On Jan 29, 2008 5:43 AM, Mike Smith <mike.smith@enterprisedb.com> wrote:
>
> You don't mention the capacity of the disks you are looking at. Here is
> something you might want to consider.
>
> I've seen a few performance posts on using different hardware technologies
> to gain improvements. Most of those comments are on raid,  interface and
> rotation speed.   One area that doesn't seem to have  been mentioned  is to
> run your disks empty.
>
> One of the key roadblocks in disk performance is the time for the disk heads
> to seek, settle and find the start of the data. Another is the time to
> transfer from disk to interface.  Everyone may instinctively know this but
> its often ignored.
>
> Hard disks are CRV ( constant rotational velocity) = they spin at the same
> speed all the time
>
> Hard disk  drives use a technology called ZBR  = Zone Bit Recording =  a lot
> more data on the outside tracks than the inner ones.
>
> Hard disk fill up from outside track to inside track  generally unless
> you've done some weird partitioning.

This really depends on your file system.  While NTFS does this, ext2/3
certainly does not.  Many unix file systems use a more random method
to distribute their writes.

The rest of what you describe is called "short stroking" in most
circles.  It's certainly worth looking into no matter what size drives
you're using.

pgsql-performance by date:

Previous
From: Gregory Stark
Date:
Subject: Re: RAID arrays and performance
Next
From: Craig James
Date:
Subject: Re: 8x2.5" or 6x3.5" disks