From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon
Date: Tue, 25 Nov 2003 15:37:42 -0800
Message-ID: <200311251537.42527.josh@agliodbs.com> (raw)
In-Reply-To: <9470.1069803647@sss.pgh.pa.us>
References: <200311251419.36771.josh@agliodbs.com>
<9470.1069803647@sss.pgh.pa.us>
Tom,
> Strictly a WAG ... but what this sounds like to me is disastrously bad
> behavior of the spinlock code under heavy contention. We thought we'd
> fixed the spinlock code for SMP machines awhile ago, but maybe
> hyperthreading opens some new vistas for misbehavior ...
Yeah, I thought of that based on the discussion on -Hackers. But we tried
turning off hyperthreading, with no change in behavior.
> If you can't try 7.4, or want to gather more data first, it would be
> good to try to confirm or disprove the theory that the context switches
> are coming from spinlock delays. If they are, they'd be coming from the
> select() calls in s_lock() in s_lock.c. Can you strace or something to
> see what kernel calls the context switches occur on?
Might be worth it ... will suggest that. Will also try 7.4.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Wierd context-switching issue on Xeon
In-Reply-To: <200311251537.42527.josh@agliodbs.com>
* 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