pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: pg@fastcrypt.com
Cc: Robert Creager <Robert_Creager@LogicalChaos.org>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Dirk_Lutzebäck <lutzeb@aeccom.com>
Cc: ohp@pyrenet.fr, Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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 21:20:20 -0400 (EDT)
Message-ID: <200405200120.i4K1KKm06350@candle.pha.pa.us> (raw)
In-Reply-To: <1083512362.25096.131.camel@localhost.localdomain>


Did we ever come to a conclusion about excessive SMP context switching
under load?

---------------------------------------------------------------------------

Dave Cramer wrote:
> Robert,
> 
> The real question is does it help under real life circumstances ? 
> 
> Did you do the tests with Tom's sql code that is designed to create high
> context switchs ?
> 
> Dave
> On Sun, 2004-05-02 at 11:20, Robert Creager wrote:
> > Found some co-workers at work yesterday to load up my library...
> > 
> > The sample period is 5 minutes long (vs 2 minutes previously):
> > 
> > Context switches -          avg    max
> > 
> > Default 7.4.1 code :       48784 107354
> > Default patch - 10 :       20400  28160
> > patch at 100       :       38574  85372
> > patch at 1000      :       41188 106569
> > 
> > The reading at 1000 was not produced under the same circumstances as the prior
> > readings as I had to replace my device under test with a simulated one.  The
> > real one died.
> > 
> > The previous run with smaller database and 120 second averages:
> > 
> > Context switches -          avg    max
> > 
> > Default 7.4.1 code :       10665  69470
> > Default patch - 10 :       17297  21929
> > patch at 100       :       26825  87073
> > patch at 1000      :       37580 110849
> -- 
> Dave Cramer
> 519 939 0336
> ICQ # 14675561
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
> 

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