pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Hayward <xelah-pgsql@xelah.com>
To: pgsql-performance@postgresql.org
Subject: Re: performance problems.
Date: Wed, 30 Aug 2006 19:22:18 +0100 (BST)
Message-ID: <Pine.LNX.4.58.0608301912570.28033@sphinx.mythic-beasts.com> (raw)
In-Reply-To: <20060830162657.GD81373@pervasive.com>
References: <44F55A7F.40305@sorbs.net>
	<BA0105C5-8551-49A6-B131-00D814DDFDA0@khera.org>
	<20060830162657.GD81373@pervasive.com>

On Wed, 30 Aug 2006, Jim C. Nasby wrote:

> On Wed, Aug 30, 2006 at 10:10:28AM -0400, Vivek Khera wrote:
> > effective_cache_size = 27462            # `sysctl -n
> > vfs.hibufspace` / 8192 (BLKSZ)
> > random_page_cost = 2
>
> You misunderstand how effective_cache_size is used. It's the *only*
> memory factor that plays a role in cost estimator functions. This means
> it should include the memory set aside for caching in shared_buffers.
>
> Also, hibufspace is only talking about filesystem buffers in FreeBSD,
> which AFAIK has nothing to do with total memory available for caching,
> since VM pages are also used to cache data.

I believe it's not talking about quantities of buffers at all, but about
kernel virtual address space. It's something like the amount of kernel
virtual address space available for mapping buffer-cache pages in to
kernel memory. It certainly won't tell you (or even approximate) how much
PostgreSQL data is being cached by the OS. Cached PostgreSQL data will
appear in the active, inactive and cached values - and (AFAIK) there isn't
any distinction between file-backed pages and swap-backed pages amongst
those.



view thread (13+ messages)  latest in thread

Message-ID: <Pine.LNX.4.58.0608301912570.28033@sphinx.mythic-beasts.com>
Permalink:  ../Pine.LNX.4.58.0608301912570.28033@sphinx.mythic-beasts.com/
Also on:    postgresql.org/message-id/Pine.LNX.4.58.0608301912570.28033@sphinx.mythic-beasts.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: xelah-pgsql@xelah.com
  Subject: Re: performance problems.
  In-Reply-To: <Pine.LNX.4.58.0608301912570.28033@sphinx.mythic-beasts.com>
  References: <44F55A7F.40305@sorbs.net> <BA0105C5-8551-49A6-B131-00D814DDFDA0@khera.org> <20060830162657.GD81373@pervasive.com> <Pine.LNX.4.58.0608301912570.28033@sphinx.mythic-beasts.com>

* 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