From: Kevin Brown <kevin@sysexperts.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Fri, 15 Apr 2005 17:58:25 -0700
Message-ID: <20050416005824.GG19518@filer> (raw)
In-Reply-To: <9fde2d603a18b53b5b3f22ad47f3a064@khera.org>
References: <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>
<20050415020337.GD19518@filer>
<9fde2d603a18b53b5b3f22ad47f3a064@khera.org>
Vivek Khera wrote:
>
> On Apr 14, 2005, at 10:03 PM, Kevin Brown wrote:
>
> >Now, bad block remapping destroys that guarantee, but unless you've
> >got a LOT of bad blocks, it shouldn't destroy your performance, right?
> >
>
> ALL disks have bad blocks, even when you receive them. you honestly
> think that these large disks made today (18+ GB is the smallest now)
> that there are no defects on the surfaces?
Oh, I'm not at all arguing that you won't have bad blocks. My
argument is that the probability of any given block read or write
operation actually dealing with a remapped block is going to be
relatively small, unless the fraction of bad blocks to total blocks is
large (in which case you basically have a bad disk). And so the
ability to account for remapped blocks shouldn't itself represent a
huge improvement in overall throughput.
--
Kevin Brown kevin@sysexperts.com
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: kevin@sysexperts.com
Subject: Re: How to improve db performance with $7K?
In-Reply-To: <20050416005824.GG19518@filer>
* 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