From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
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: 18 Apr 2004 20:40:35 -0400
Message-ID: <87d6647qbg.fsf@stark.xeocode.com> (raw)
In-Reply-To: <11437.1082324861@sss.pgh.pa.us>
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>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> So in the short term I think we have to tell people that Xeon MP is not
> the most desirable SMP platform to run Postgres on. (Josh thinks that
> the specific motherboard chipset being used in these machines might
> share some of the blame too. I don't have any evidence for or against
> that idea, but it's certainly possible.)
>
> In the long run, however, CPUs continue to get faster than main memory
> and the price of cache contention will continue to rise. So it seems
> that we need to give up the assumption that SpinLockAcquire is a cheap
> operation. In the presence of heavy contention it won't be.
There's nothing about the way Postgres spinlocks are coded that affects this?
Is it something the kernel could help with? I've been wondering whether
there's any benefits postgres is missing out on by using its own hand-rolled
locking instead of using the pthreads infrastructure that the kernel is often
involved in.
--
greg
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: gsstark@mit.edu, tgl@sss.pgh.pa.us, josh@agliodbs.com, neilc@samurai.com
Subject: Re: Wierd context-switching issue on Xeon
In-Reply-To: <87d6647qbg.fsf@stark.xeocode.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