pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Manfred Spraul <manfred@colorfullife.com>
Cc: neilc@samurai.com
Cc: markw@osdl.org
Subject: Re: futex results with dbt-3
Date: Tue, 19 Oct 2004 14:59:48 -0700
Message-ID: <200410191459.48080.josh@agliodbs.com> (raw)
In-Reply-To: <20151.1098222733@sss.pgh.pa.us>
References: <417221B5.1050704@colorfullife.com>
	<20151.1098222733@sss.pgh.pa.us>

Tom,

> 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

Josh Berkus
Aglio Database Solutions
San Francisco



view thread (24+ messages)  latest in thread

Message-ID: <200410191459.48080.josh@agliodbs.com>
Permalink:  ../200410191459.48080.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200410191459.48080.josh@agliodbs.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: josh@agliodbs.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: <200410191459.48080.josh@agliodbs.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