pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: J. Andrew Rogers <jrogers@neopolitan.com>
Cc: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: First set of OSDL Shared Mem scalability results,
Date: Fri, 08 Oct 2004 18:32:32 -0400
Message-ID: <21489.1097274752@sss.pgh.pa.us> (raw)
In-Reply-To: <1097273580.25588.18.camel@vulture.corp.neopolitan.com>
References: <200410081443.16109.josh@agliodbs.com>
	<1097273580.25588.18.camel@vulture.corp.neopolitan.com>

"J. Andrew Rogers" <jrogers@neopolitan.com> writes:
> As I understand it (and I haven't looked so I could be wrong), the
> buffer cache is searched by traversing it sequentially.

You really should look first.

The main-line code paths use hashed lookups.  There are some cases that
do linear searches through the buffer headers or the CDB lists; in
theory those are supposed to be non-performance-critical cases, though
I am suspicious that some are not (see other response).  In any case,
those structures are considerably more compact than the buffers proper,
and I doubt that cache misses per se are the killer factor.

This does raise a question for Josh though, which is "where's the
oprofile results?"  If we do have major problems at the level of cache
misses then oprofile would be able to prove it.

			regards, tom lane



view thread (41+ messages)  latest in thread

Message-ID: <21489.1097274752@sss.pgh.pa.us>
Permalink:  ../21489.1097274752@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21489.1097274752@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, jrogers@neopolitan.com, josh@agliodbs.com
  Subject: Re: First set of OSDL Shared Mem scalability results,
  In-Reply-To: <21489.1097274752@sss.pgh.pa.us>

* 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