From: Tom Lane <tgl@sss.pgh.pa.us>
To: pg@fastcrypt.com
Cc: lutzeb@aeccom.com, Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgreSQL.org, Neil Conway <neilc@samurai.com>
Subject: Re: Wierd context-switching issue on Xeon
Date: Sun, 18 Apr 2004 22:20:22 -0400
Message-ID: <13960.1082341222@sss.pgh.pa.us> (raw)
In-Reply-To: <1082331281.1557.47.camel@localhost.localdomain>
References: <200311251419.36771.josh@agliodbs.com>
<200404151039.17763.josh@agliodbs.com>
<407EE93F.3090705@aeccom.com>
<200404151335.27762.josh@agliodbs.com>
<407EFC95.5070805@aeccom.com>
<11437.1082324861@sss.pgh.pa.us>
<1082331281.1557.47.camel@localhost.localdomain>
Dave Cramer <pg@fastcrypt.com> writes:
> So the the kernel/OS is irrelevant here ? this happens on any dual xeon?
I believe so. The context-switch behavior might possibly be a little
more pleasant on other kernels, but the underlying spinlock problem is
not dependent on the kernel.
> 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.
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: tgl@sss.pgh.pa.us, pg@fastcrypt.com, josh@agliodbs.com, neilc@samurai.com
Subject: Re: Wierd context-switching issue on Xeon
In-Reply-To: <13960.1082341222@sss.pgh.pa.us>
* 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