pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@qwest.net>
To: Ioannis Theoharis <theohari@ics.forth.gr>
Cc: pgsql-performance@postgresql.org
Subject: Re: Page Miss Hits
Date: Mon, 02 Aug 2004 10:19:27 -0600
Message-ID: <1091463567.27166.44.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.58.0408021111320.12597@calliope>
References: <Pine.GSO.4.58.0408021111320.12597@calliope>

On Mon, 2004-08-02 at 02:11, Ioannis Theoharis wrote:
> Hi, i would like to answer if there is any way in postgres to find the
> page miss hits caused during a query execution.
> 
> 
> Is there something like explain analyze with the page miss hits???

You're making a basic assumption that is (at least currently) untrue,
and that is that PostgreSQL has it's own cache.  It doesn't.  It has a
buffer that drops buffer back into the free pool when the last
referencing backend concludes and shuts down.  So, PostgreSQL currently
relies on the kernel to cache for it.  So, what you need is a tool that
monitors the kernel cache usage and its hit rate.  I'm not familiar with
any, but I'm sure something out there likely does that.




view thread (6+ messages)  latest in thread

Message-ID: <1091463567.27166.44.camel@localhost.localdomain>
Permalink:  ../1091463567.27166.44.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1091463567.27166.44.camel@localhost.localdomain

 · 

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: smarlowe@qwest.net, theohari@ics.forth.gr
  Subject: Re: Page Miss Hits
  In-Reply-To: <1091463567.27166.44.camel@localhost.localdomain>

* 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