Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] [PATCHES] ARC Memory Usage analysis

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Thomas F(dot)O'Connell <tfo(at)sitening(dot)com>,Simon Riggs <simon(at)2ndquadrant(dot)com>,PgSQL - Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: [PERFORM] [PATCHES] ARC Memory Usage analysis
Date: 2004-10-27 00:39:59
Message-ID: 200410261739.59814.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patchespgsql-performance
Thomas,

> 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?

Currently, yes.  Right now, e_c_s is used just to inform the planner and make 
index vs. table scan and join order decisions.

The problem which Simon is bringing up is part of a discussion about doing 
*more* with the information supplied by e_c_s.    He points out that it's not 
really related to the *real* probability of any particular table being 
cached.   At least, if I'm reading him right.

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2004-10-27 00:42:53
Subject: Re: can't handle large number of INSERT/UPDATEs
Previous:From: Thomas F.O'ConnellDate: 2004-10-27 00:09:22
Subject: Re: [PATCHES] [HACKERS] ARC Memory Usage analysis

pgsql-hackers by date

Next:From: Neil ConwayDate: 2004-10-27 00:52:43
Subject: Re: New compile warnings in CVS
Previous:From: Thomas F.O'ConnellDate: 2004-10-27 00:09:22
Subject: Re: [PATCHES] [HACKERS] ARC Memory Usage analysis

pgsql-patches by date

Next:From: Bruce MomjianDate: 2004-10-27 00:43:13
Subject: Re: pg_ctl -D canonicalization
Previous:From: Thomas F.O'ConnellDate: 2004-10-27 00:09:22
Subject: Re: [PATCHES] [HACKERS] ARC Memory Usage analysis

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group