pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pg@fastcrypt.com, Robert Creager <Robert_Creager@LogicalChaos.org>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Dirk_Lutzebäck <lutzeb@aeccom.com>
Cc: ohp@pyrenet.fr, Joe Conway <mail@joeconway.com>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-performance@postgresql.org, Neil Conway <neilc@samurai.com>
Subject: Re: Wierd context-switching issue on Xeon
Date: Wed, 19 May 2004 23:02:16 -0400 (EDT)
Message-ID: <200405200302.i4K32G721749@candle.pha.pa.us> (raw)
In-Reply-To: <24373.1085020886@sss.pgh.pa.us>

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Did we ever come to a conclusion about excessive SMP context switching
> > under load?
> 
> Yeah: it's bad.
> 
> Oh, you wanted a fix?  That seems harder :-(.  AFAICS we need a redesign
> that causes less load on the BufMgrLock.  However, the traditional
> solution to too-much-contention-for-a-lock is to break up the locked
> data structure into finer-grained units, which means *more* lock
> operations in total.  Normally you expect that the finer-grained lock
> units will mean less contention.  But given that the issue here seems to
> be trading physical ownership of the lock's cache line back and forth,
> I'm afraid that the traditional approach would actually make things
> worse.  The SMP issue seems to be not with whether there is
> instantaneous contention for the locked datastructure, but with the cost
> of making it possible for processor B to acquire a lock recently held by
> processor A.

I see.  I don't even see a TODO in there.  :-(

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (77+ messages)  latest in thread

Message-ID: <200405200302.i4K32G721749@candle.pha.pa.us>
Permalink:  ../200405200302.i4K32G721749@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200405200302.i4K32G721749@candle.pha.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: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, Robert_Creager@LogicalChaos.org, josh@agliodbs.com, lutzeb@aeccom.com, mail@joeconway.com, scott.marlowe@ihs.com, neilc@samurai.com
  Subject: Re: Wierd context-switching issue on Xeon
  In-Reply-To: <200405200302.i4K32G721749@candle.pha.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