pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pg@fastcrypt.com
Cc: Paul Tuckfield <paul@tuckfield.com>
Cc: Anjan Dave <adave@vantage.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Neil Conway <neilc@samurai.com>
Cc: Dirk Lutzebäck <lutzeb@aeccom.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
Date: Wed, 21 Apr 2004 22:35:30 -0400
Message-ID: <18322.1082601330@sss.pgh.pa.us> (raw)
In-Reply-To: <1082580588.13371.260.camel@localhost.localdomain>
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>
	<1082574808.1558.243.camel@localhost.localdomain>
	<1082580588.13371.260.camel@localhost.localdomain>

Dave Cramer <pg@fastcrypt.com> writes:
> diff -c -r1.16 s_lock.c
> *** backend/storage/lmgr/s_lock.c	8 Aug 2003 21:42:00 -0000	1.16
> --- backend/storage/lmgr/s_lock.c	21 Apr 2004 20:27:34 -0000
> ***************
> *** 76,82 ****
>   	 * The select() delays are measured in centiseconds (0.01 sec) because 10
>   	 * msec is a common resolution limit at the OS level.
>   	 */
> ! #define SPINS_PER_DELAY		100
>   #define NUM_DELAYS			1000
>   #define MIN_DELAY_CSEC		1
>   #define MAX_DELAY_CSEC		100
> --- 76,82 ----
>   	 * The select() delays are measured in centiseconds (0.01 sec) because 10
>   	 * msec is a common resolution limit at the OS level.
>   	 */
> ! #define SPINS_PER_DELAY		10
>   #define NUM_DELAYS			1000
>   #define MIN_DELAY_CSEC		1
>   #define MAX_DELAY_CSEC		100


As far as I can tell, this does reduce the rate of semop's
significantly, but it does so by bringing the overall processing rate
to a crawl :-(.  I see 97% CPU idle time when using this patch.
I believe what is happening is that the select() delay in s_lock.c is
being hit frequently because the spin loop isn't allowed to run long
enough to let the other processor get out of the spinlock.

			regards, tom lane



view thread (22+ messages)  latest in thread

Message-ID: <18322.1082601330@sss.pgh.pa.us>
Permalink:  ../18322.1082601330@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/18322.1082601330@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, pg@fastcrypt.com, paul@tuckfield.com, adave@vantage.com, josh@agliodbs.com, neilc@samurai.com, lutzeb@aeccom.com
  Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
  In-Reply-To: <18322.1082601330@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