From: Grzegorz Jaśkiewicz <gryzman@gmail.com>
To: Jeff <threshar@torgo.978.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: random_page_cost vs ssd?
Date: Wed, 11 Mar 2009 15:37:55 +0000
Message-ID: <2f4958ff0903110837x21aa4c75m4473d053127c043d@mail.gmail.com> (raw)
In-Reply-To: <B1349331-0035-4FFE-80E9-91A4B168F4DB@torgo.978.org>
References: <B1349331-0035-4FFE-80E9-91A4B168F4DB@torgo.978.org>
On Wed, Mar 11, 2009 at 1:46 PM, Jeff <threshar@torgo.978.org> wrote:
> I've got a couple x25-e's in production now and they are working like a
> champ. (In fact, I've got another box being built with all x25s in it. its
> going to smoke!)
>
> Anyway, I was just reading another thread on here and that made me wonder
> about random_page_cost in the world of an ssd where a seek is basically
> free. I haven't tested this yet (I can do that next week), but logically,
> in this scenario wouldn't lowering random_page_cost be ideal or would it not
> really matter in the grand scheme of things?
Just on a side note, random access on SSD is still more expensive than
sequential, because it is designed in banks.
If you don believe me, turn off any software/OS cache , and try random
access timing against seq reads.
This gap is just much much narrower.
--
GJ
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: gryzman@gmail.com, threshar@torgo.978.org
Subject: Re: random_page_cost vs ssd?
In-Reply-To: <2f4958ff0903110837x21aa4c75m4473d053127c043d@mail.gmail.com>
References: <B1349331-0035-4FFE-80E9-91A4B168F4DB@torgo.978.org> <2f4958ff0903110837x21aa4c75m4473d053127c043d@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