From: Dave Cramer <pg@fastcrypt.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joe Conway <mail@joeconway.com>
Cc: Dirk Lutzebäck <lutzeb@aeccom.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Toooo many context switches (maybe SLES8?)
Date: Sun, 18 Apr 2004 14:49:53 -0400
Message-ID: <1082314193.1557.44.camel@localhost.localdomain> (raw)
In-Reply-To: <200404151337.00273.josh@agliodbs.com>
References: <407E7B99.3050306@aeccom.com>
<407EBA89.6080007@joeconway.com>
<20498.1082057841@sss.pgh.pa.us>
<200404151337.00273.josh@agliodbs.com>
Isn't this a linux kernel issue ?
My understanding is that the scheduler doesn't know that 2 of the CPU's
are actually the same underlying hardware and sometimes two contexts end
up fighting for the same underlying chip?
--dc--
On Thu, 2004-04-15 at 16:37, Josh Berkus wrote:
> Folks,
>
> > I am currently chasing what seems to be the same issue: massive context
> > swapping on a dual Xeon system. I tried back-patching the above-mentioned
> > patch ... it helps a little but by no means solves the problem ...
>
> BTW, I'm currently pursuing the possibility that this has something to do with
> the ServerWorks chipset on those motherboards. If anyone knows a high-end
> hardware+linux kernel geek I can corner, I'd appreciate it.
>
> Maybe I should contact OSDL ...
--
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, mail@joeconway.com, lutzeb@aeccom.com
Subject: Re: Toooo many context switches (maybe SLES8?)
In-Reply-To: <1082314193.1557.44.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