Skip site navigation (1) Skip section navigation (2)

Re: futex results with dbt-3

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Manfred Spraul <manfred(at)colorfullife(dot)com>, neilc(at)samurai(dot)com,markw(at)osdl(dot)org
Subject: Re: futex results with dbt-3
Date: 2004-10-19 21:59:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance

> 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;
> and if so, we could read their code and adopt that method without having
> to buy into any large reorganization of our code.

Well, initial results from Gavin/Neil's patch seem to indicate that, while 
futexes do not cure the CSStorm bug, they do lessen its effects in terms of 
real performance loss.


Josh Berkus
Aglio Database Solutions
San Francisco

In response to


pgsql-performance by date

Next:From: Kevin BarnardDate: 2004-10-19 22:09:21
Subject: Re: [PERFORM] Performance on Win32 vs Cygwin
Previous:From: Tom LaneDate: 2004-10-19 21:52:13
Subject: Re: futex results with dbt-3

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group