Re: Toooo many context switches (maybe SLES8?)

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: lutzeb(at)aeccom(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Toooo many context switches (maybe SLES8?)
Date: 2004-04-20 14:50:52
Message-ID: 1082472652.1554.155.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Don't think so, mine is a vanilla kernel from kernel.org

Dave
On Thu, 2004-04-15 at 16:03, Dirk Lutzebaeck wrote:
> 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(at)joeconway(dot)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
> >
> >
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
>
>
> !DSPAM:408535ce93801252113544!
>
>
--
Dave Cramer
519 939 0336
ICQ # 14675561

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2004-04-20 15:48:09 pgbench written in Pro*C
Previous Message Dirk Lutzebäck 2004-04-20 14:29:01 Re: Wierd context-switching issue on Xeon