From: johnnnnnn <john@phaedrusdeinus.org>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Scaling further up
Date: Tue, 2 Mar 2004 17:25:41 -0600
Message-ID: <20040302232540.GA4102@performics.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0403021411570.4475-100000@css120.ihs.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF785098039@vt-pe2550-001.vantage.vantage.com>
<Pine.LNX.4.33.0403021411570.4475-100000@css120.ihs.com>
On Tue, Mar 02, 2004 at 02:16:24PM -0700, scott.marlowe wrote:
> It's a common misconception that faster RPM drives are a lot faster,
> when, in fact, their only speed advantage is slight faster seeks.
> The areal density of faster spinning hard drives tends to be
> somewhat less than the slower spinning drives, since the maximum
> frequency the heads can work in on both drives, assuming the same
> technology, is the same. I.e. the speed at which you can read data
> off of the platter doesn't usually go up with a higher RPM drive,
> only the speed with which you can get to the first sector.
This would imply that an upgrade in drive RPM should be accompanied by
a decrease in random_page_cost, correct?
random_page_cost should be set with the following things taken into
account:
- seek speed
- likelihood of page to be cached in memory by the kernel
- anything else?
Sorry, i realize this pulls the thread a bit off-topic, but i've heard
that about RPM speeds before, and i just want some confirmation that
my deductions are reasonable.
-johnnnnnnnnnnn
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: john@phaedrusdeinus.org, scott.marlowe@ihs.com
Subject: Re: Scaling further up
In-Reply-To: <20040302232540.GA4102@performics.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