From: Dirk.Lutzebaeck@t-online.de
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joe Conway <mail@joeconway.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Toooo many context switches (maybe SLES8?)
Date: Thu, 15 Apr 2004 22:03:39 +0200
Message-ID: <407EEA9B.7010807@aeccom.com> (raw)
In-Reply-To: <20498.1082057841@sss.pgh.pa.us>
References: <407E7B99.3050306@aeccom.com>
<407EB1E5.4030600@joeconway.com>
<407EB86B.6080801@aeccom.com>
<407EBA89.6080007@joeconway.com>
<20498.1082057841@sss.pgh.pa.us>
Could this be related to the O(1) scheduler backpatches from 2.6 to 2.4
kernel on newer 2.4er distros (RedHat, SuSE)?
Tom Lane wrote:
>Joe Conway <mail@joeconway.com> writes:
>
>
>>>Improve spinlock code for recent x86 processors: insert a PAUSE
>>>instruction in the s_lock() wait loop, and use test before test-and-set
>>>in TAS() macro to avoid unnecessary bus traffic. Patch from Manfred
>>>Spraul, reworked a bit by Tom.
>>>
>>>
>
>
>
>>I thought this had been committed to the 7.4 stable branch as well, but
>>it appears not.
>>
>>
>
>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 ...
>
> regards, tom lane
>
>
>
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: Dirk.Lutzebaeck@t-online.de, tgl@sss.pgh.pa.us, mail@joeconway.com
Subject: Re: Toooo many context switches (maybe SLES8?)
In-Reply-To: <407EEA9B.7010807@aeccom.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