Re: random_page_cost = 2.0 on Heroku Postgres

On 08/02/12 21:15, Peter van Hardenberg wrote:
> Having read the thread, I don't really see how I could study what a
> more principled value would be.
>
> That said, I have access to a very large fleet in which to can collect
> data so I'm all ears for suggestions about how to measure and would
> gladly share the results with the list.
>
> Peter
>
> On Wed, Feb 8, 2012 at 5:39 PM, Scott Marlowe<scott(dot)marlowe(at)gmail(dot)com> wrote:
>> On Wed, Feb 8, 2012 at 5:50 PM, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
>>> On 2/7/12 4:59 PM, Peter van Hardenberg wrote:
>>>> Per the thread from last month, I've updated the default
>>>> random_page_cost on Heroku Postgres to reduce the expected cost of a
>>>> random_page on all new databases.
>>> This is because Heroku uses AWS storage, which has fast seeks but poor
>>> throughput compared to internal disk on a standard system, BTW.
>> Also judging by the other thread, it might be something to stop closer
>> to 1.2 to 1.4 or something.
>>
>> --
>> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-performance
>
>
You can execute several queries with the three different values provided
by Scott and Josh.
- SET random_page_cost = 2.0
First execution of the queries with EXPLAIN ANALYZE
- SET random_page_cost = 1.4
Second execution of the queries with EXPLAIN ANALYZE
- SET random_page_cost = 1.2
Second execution of the queries with EXPLAIN ANALYZE

And then, you can compare the pattern behind these queries executions
Regards,

--
Marcos Luis Ortíz Valmaseda
Sr. Software Engineer (UCI)
http://marcosluis2186.posterous.com
http://www.linkedin.com/in/marcosluis2186
Twitter: @marcosluis2186

Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
http://www.antiterroristas.cu
http://justiciaparaloscinco.wordpress.com