Re: reducing random_page_cost from 4 to 2 to force index scan - Mailing list pgsql-performance

From Stuart Bishop
Subject Re: reducing random_page_cost from 4 to 2 to force index scan
Date
Msg-id BANLkTikcVUeRfocJPe_W+jfi5k1+gcLnxg@mail.gmail.com
Whole thread Raw
In response to Re: reducing random_page_cost from 4 to 2 to force index scan  (Josh Berkus <josh@agliodbs.com>)
Responses Re: reducing random_page_cost from 4 to 2 to force index scan  (Josh Berkus <josh@agliodbs.com>)
List pgsql-performance
On Sat, May 14, 2011 at 3:13 AM, Josh Berkus <josh@agliodbs.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@stuartbishop.net>
http://www.stuartbishop.net/

pgsql-performance by date:

Previous
From: "ktm@rice.edu"
Date:
Subject: Re: Using pgiosim realistically
Next
From: Josh Berkus
Date:
Subject: Re: reducing random_page_cost from 4 to 2 to force index scan