From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org, 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 18:39:48 -0400
Message-ID: <27697.1098225588@sss.pgh.pa.us> (raw)
In-Reply-To: <200410191459.48080.josh@agliodbs.com>
References: <417221B5.1050704@colorfullife.com>
<20151.1098222733@sss.pgh.pa.us>
<200410191459.48080.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
>> The bigger problem here is that the SMP locking bottlenecks we are
>> currently seeing are *hardware* issues (AFAICT anyway).
> 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.
It would be reasonable to expect that futexes would have a somewhat more
efficient code path in the case where you have to block (mainly because
SysV semaphores have such a heavyweight API, much more complex than we
really need). However, the code path that is killing us is the one
where you *don't* actually need to block. If we had a proper fix for
the problem then the context swap storm itself would go away, and
whatever advantage you might be able to measure now for futexes likewise
would go away.
In other words, I'm not real excited about a wholesale replacement of
code in order to speed up a code path that I don't want to be taking
in the first place; especially not if that replacement puts a fence
between me and working on the code path that I do care about.
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, josh@agliodbs.com, manfred@colorfullife.com, neilc@samurai.com, markw@osdl.org
Subject: Re: futex results with dbt-3
In-Reply-To: <27697.1098225588@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