pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Manfred Spraul <manfred@colorfullife.com>
Cc: neilc@samurai.com
Cc: markw@osdl.org
Cc: pgsql-performance@postgresql.org
Subject: Re: futex results with dbt-3
Date: Wed, 20 Oct 2004 20:27:49 -0400
Message-ID: <41770285.5090604@fastcrypt.com> (raw)
In-Reply-To: <7178.1098292535@sss.pgh.pa.us>
References: <417221B5.1050704@colorfullife.com>
	<20151.1098222733@sss.pgh.pa.us>
	<417697A5.1050600@colorfullife.com>
	<7178.1098292535@sss.pgh.pa.us>

Forgive my naivete, but do futex's implement some priority algorithm for 
which process gets control. One of the problems as I understand it is 
that linux does (did ) not implement a priority algorithm, so it is 
possible for the context which just gave up control to be the next 
context woken up, which of course is a complete waste of time.

--dc--

Tom Lane wrote:

>Manfred Spraul <manfred@colorfullife.com> writes:
>  
>
>>Tom Lane wrote:
>>    
>>
>>>The bigger problem here is that the SMP locking bottlenecks we are
>>>currently seeing are *hardware* issues (AFAICT anyway).  The only way
>>>that futexes can offer a performance win is if they have a smarter way
>>>of executing the basic atomic-test-and-set sequence than we do;
>>>
>>>      
>>>
>>lwlocks operations are not a basic atomic-test-and-set sequence. They 
>>are spinlock, several nonatomic operations, spin_unlock.
>>    
>>
>
>Right, and it is the spinlock that is the problem.  See discussions a
>few months back: at least on Intel SMP machines, most of the problem
>seems to have to do with trading the spinlock's cache line back and
>forth between CPUs.  It's difficult to see how a futex is going to avoid
>that.
>
>			regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>      subscribe-nomail command to majordomo@postgresql.org so that your
>      message can get through to the mailing list cleanly
>
>
>  
>

-- 
Dave Cramer
www.postgresintl.com
519 939 0336
ICQ#14675561




view thread (24+ messages)  latest in thread

Message-ID: <41770285.5090604@fastcrypt.com>
Permalink:  ../41770285.5090604@fastcrypt.com/
Also on:    postgresql.org/message-id/41770285.5090604@fastcrypt.com

 · 

reply

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: pg@fastcrypt.com, tgl@sss.pgh.pa.us, manfred@colorfullife.com, neilc@samurai.com, markw@osdl.org
  Subject: Re: futex results with dbt-3
  In-Reply-To: <41770285.5090604@fastcrypt.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