pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Paul Thomas <paul@tmsl.demon.co.uk>
To: scott . marlowe <scott.marlowe@ihs.com>
Cc: pgsql-performance @ postgresql . org <pgsql-performance@postgresql.org>
Subject: Re: Scaling further up
Date: Thu, 4 Mar 2004 00:52:08 +0000
Message-ID: <20040304005208.A25816@bacon> (raw)
In-Reply-To: <Pine.LNX.4.33.0403031113580.8268-100000@css120.ihs.com>
References: <20040303085718.A24535@bacon>
	<Pine.LNX.4.33.0403031113580.8268-100000@css120.ihs.com>

On 03/03/2004 18:23 scott.marlowe wrote:
> [snip]
> There are three factors that affect how fast you can get to the next
> sector:
> 
> seek time
> settle time
> rotational latency
> 
> Most drives only list the first, and don't bother to mention the other
> two.

Ah yes, one of my (very) few still functioning brain cells was nagging 
about another bit of time in the equation :)

> On many modern drives, the seek times are around 5 to 10 milliseconds.
> [snip]

Going back to the OPs posting about random_page_cost, imagine I have 2 
servers identical in every way except the disk drive. Server A has a 10K 
rpm drive and server B has a 15K rpm drive. Seek/settle times aren't 
spectacularly different between the 2 drives. I'm wondering if drive B 
might actually merit a _higher_ random_page_cost than drive A as, once it 
gets settled on a disk track, it can suck the data off a lot faster. 
opinions/experiences anyone?


-- 
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller 
Business |
| Computer Consultants         | 
http://www.thomas-micro-systems-ltd.co.uk   |
+------------------------------+---------------------------------------------+



view thread (35+ messages)  latest in thread

Message-ID: <20040304005208.A25816@bacon>
Permalink:  ../20040304005208.A25816@bacon/
Also on:    postgresql.org/message-id/20040304005208.A25816@bacon

 · 

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: paul@tmsl.demon.co.uk, scott.marlowe@ihs.com
  Subject: Re: Scaling further up
  In-Reply-To: <20040304005208.A25816@bacon>

* 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