Re: random_page_cost configuration parameter

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Mathias Kunter <mathiaskunter(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: random_page_cost configuration parameter
Date: 2022-01-07 21:52:56
Message-ID: Ydi2OIrmRtV9fS0o@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, Jan 5, 2022 at 07:27:55PM +0100, Mathias Kunter wrote:
> Am 28.12.21 um 17:03 schrieb Tom Lane:
> > Mathias Kunter <mathiaskunter(at)gmail(dot)com> writes:
> > > Consider the situation
> > > where the randomly fetched pages are mostly (or even entirely) cached in
> > > RAM, but where the sequentially fetched pages must be mostly read from
> > > disk. An example for such a scenario is a database system which uses
> > > RAM-cached indices.
> >
> > I think fooling with effective_cache_size is a better way to model
> > that situation.
>
> The default value of effective_cache_size is 4 GB. Which value should be
> used instead on a system which only has 4 GB of total RAM, but still uses
> RAM-cached indices?

This might help:

https://momjian.us/main/blogs/pgblog/2012.html#May_4_2012

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Shinya Kato 2022-01-11 07:40:22 Question about role attributes docs
Previous Message Tom Lane 2022-01-07 16:41:56 Re: "(process)" is missing for some terms about process in glossary