Re: reducing random_page_cost from 4 to 2 to force index scan

From: Stuart Bishop <stuart(at)stuartbishop(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan
Date: 2011-05-15 03:49:02
Message-ID: BANLkTikcVUeRfocJPe_W+jfi5k1+gcLnxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sat, May 14, 2011 at 3:13 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:

> This is what the combination of random_page_cost and
> effective_cache_size ought to supply, but I don't think it does, quite.

I think random_page_cost causes problems because I need to combine
disk random access time, which I can measure, with a guesstimate of
the disk cache hit rate. It would be lovely if these two variables
were separate. It would be even lovelier if the disk cache hit rate
could be probed at run time and didn't need setting at all, but I
suspect that isn't possible on some platforms.

--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2011-05-15 18:08:53 Re: reducing random_page_cost from 4 to 2 to force index scan
Previous Message ktm@rice.edu 2011-05-14 17:07:02 Re: Using pgiosim realistically