From: Dave Cramer <pg@fastcrypt.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Paul Tuckfield <paul@tuckfield.com>
Cc: Anjan Dave <adave@vantage.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 23:18:47 -0400
Message-ID: <1082603927.1558.279.camel@localhost.localdomain> (raw)
In-Reply-To: <200404211953.24898.josh@agliodbs.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814A@vt-pe2550-001.vantage.vantage.com>
<1082580588.13371.260.camel@localhost.localdomain>
<18322.1082601330@sss.pgh.pa.us>
<200404211953.24898.josh@agliodbs.com>
More data....
On a dual xeon with HTT enabled:
I tried increasing the NUM_SPINS to 1000 and it works better.
NUM_SPINLOCKS CS ID pgbench
100 250K 59% 230 TPS
1000 125K 55% 228 TPS
This is certainly heading in the right direction ? Although it looks
like it is highly dependent on the system you are running on.
--dc--
On Wed, 2004-04-21 at 22:53, Josh Berkus wrote:
> Tom,
>
> > 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.
>
> Also, I tested it on production data, and it reduces the CSes by about 40%.
> An improvement, but not a magic bullet.
--
Dave Cramer
519 939 0336
ICQ # 14675561
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: pg@fastcrypt.com, josh@agliodbs.com, tgl@sss.pgh.pa.us, paul@tuckfield.com, adave@vantage.com, neilc@samurai.com, lutzeb@aeccom.com
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
In-Reply-To: <1082603927.1558.279.camel@localhost.localdomain>
* 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