=?ISO-8859-1?Q?Pailloncy_Jean-G=E9rard?= <pailloncy@ifrance.com> writes:
> I run the following command three times to prevent cache/disk results.
Do you think that's actually representative of how your database will
behave under load?
If the DB is small enough to be completely cached in RAM, and you
expect it to remain so, then it's sensible to optimize on the basis
of fully-cached test cases. Otherwise I think you are optimizing
the wrong thing.
If you do want to plan on this basis, you want to set random_page_cost
to 1, make sure effective_cache_size is large, and perhaps increase
the cpu_xxx cost numbers. (What you're essentially doing here is
reducing the estimated cost of a page fetch relative to CPU effort.)
regards, tom lane