pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kenneth Marshall <ktm@is.rice.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon
Date: Wed, 21 Apr 2004 21:45:54 -0400
Message-ID: <17856.1082598354@sss.pgh.pa.us> (raw)
In-Reply-To: <20040421220231.GA18010@it.is.rice.edu>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814A@vt-pe2550-001.vantage.vantage.com>
	<200404200959.52813.josh@agliodbs.com>
	<1082515263.1558.214.camel@localhost.localdomain>
	<78427208-93C0-11D8-BA67-000393BD6C3E@tuckfield.com>
	<14264.1082573491@sss.pgh.pa.us>
	<20040421220231.GA18010@it.is.rice.edu>

Kenneth Marshall <ktm@is.rice.edu> writes:
> If the context swap storm derives from LWLock contention, maybe using
> a random order to assign buffer locks in buf_init.c would prevent
> simple adjacency of buffer allocation to cause the storm.

Good try, but no cigar ;-).  The test cases I've been looking at take
only shared locks on the per-buffer locks, so that's not where the
context swaps are coming from.  The swaps have to be caused by the
BufMgrLock, because that's the only exclusive lock being taken.

I did try increasing the allocated size of the spinlocks to 128 bytes
to see if it would do anything.  It didn't ...

			regards, tom lane



view thread (77+ messages)  latest in thread

Message-ID: <17856.1082598354@sss.pgh.pa.us>
Permalink:  ../17856.1082598354@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17856.1082598354@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, ktm@is.rice.edu
  Subject: Re: Wierd context-switching issue on Xeon
  In-Reply-To: <17856.1082598354@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