pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: [PATCHES] [HACKERS] ARC Memory Usage analysis
Date: Mon, 01 Nov 2004 02:11:45 +0100
Message-ID: <cm42gu$14nu$1@news.hub.org> (raw)
In-Reply-To: <74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com>
References: <1098471059.20926.49.camel@localhost.localdomain>
	<41796115.2020501@Yahoo.com>
	<20041022200955.GC4382@it.is.rice.edu>
	<417D1D01.3090401@Yahoo.com>
	<20651.1098720192@sss.pgh.pa.us>
	<1098780555.6807.136.camel@localhost.localdomain>
	<74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com>

Thomas F.O'Connell wrote:
> 
> As a result, I was intending to inflate the value of 
> effective_cache_size to closer to the amount of unused RAM on some of 
> the machines I admin (once I've verified that they all have a unified 
> buffer cache). Is that correct?
> 

Effective cache size is IMHO a "bogus" parameter on postgresql.conf,
this because:

1) That parameter is not intended to instruct postgres to use that ram but
    is only an hint to the engine on what the "DBA" *believe* the OS cache
    memory for postgres
2) This parameter change only the cost evaluation of plans ( and not soo
    much )

so don't hope to double this parameter and push postgres to use more RAM.



Regards
Gaetano Mendola







view thread (32+ messages)  latest in thread

Message-ID: <cm42gu$14nu$1@news.hub.org>
Permalink:  ../cm42gu$14nu$1@news.hub.org/
Also on:    postgresql.org/message-id/cm42gu$14nu$1@news.hub.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mendola@bigfoot.com
  Subject: Re: [PATCHES] [HACKERS] ARC Memory Usage analysis
  In-Reply-To: <cm42gu$14nu$1@news.hub.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox