Re: Wierd context-switching issue on Xeon - Mailing list pgsql-performance

From Dave Cramer
Subject Re: Wierd context-switching issue on Xeon
Date
Msg-id 1082377953.1554.77.camel@localhost.localdomain
Whole thread Raw
In response to Re: Wierd context-switching issue on Xeon  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Here's an interesting link that suggests that hyperthreading would be
much worse.


http://groups.google.com/groups?q=hyperthreading+dual+xeon+idle&start=10&hl=en&lr=&ie=UTF-8&c2coff=1&selm=aukkonen-FE5275.21093624062003%40shawnews.gv.shawcable.net&rnum=16

another which has some hints as to how it should be handled


http://groups.google.com/groups?q=hyperthreading+dual+xeon+idle&start=10&hl=en&lr=&ie=UTF-8&c2coff=1&selm=u5tl1XD3BHA.2760%40tkmsftngp04&rnum=19
FWIW, I have anecdotal evidence that suggests that this is the case, on
of my clients was seeing very large context switches with HTT turned on,
and without it was much better.

Dave
On Sun, 2004-04-18 at 23:19, Tom Lane wrote:
> >> What about hypterthreading does it still happen if HTT is turned off ?
>
> > The problem comes from keeping the caches synchronized between multiple
> > physical CPUs.  AFAICS enabling HTT wouldn't make it worse, because a
> > hyperthreaded processor still only has one cache.
>
> Also, I forgot to say that the numbers I'm quoting *are* with HTT off.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
>
>
> !DSPAM:40834781158911062514350!
>
>
--
Dave Cramer
519 939 0336
ICQ # 14675561


pgsql-performance by date:

Previous
From: Greg Stark
Date:
Subject: Re: Horribly slow hash join
Next
From: Rod Taylor
Date:
Subject: Re: very slow simple query - outer join makes it quicker