From: Gaetano Mendola <mendola@bigfoot.com>
To: Josh Berkus <josh@agliodbs.com>
Subject: Re: futex results with dbt-3
Date: Sat, 23 Oct 2004 12:51:39 +0200
Message-ID: <417A37BB.9050305@bigfoot.com> (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 wrote:
> 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.
I proposed weeks ago to see how the CSStorm is affected by stick each backend
in one processor ( where the process was born ) using the cpu-affinity capability
( kernel 2.6 ), is this proposal completely out of mind ?
Regards
Gaetano Mendola
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: mendola@bigfoot.com, josh@agliodbs.com
Subject: Re: futex results with dbt-3
In-Reply-To: <417A37BB.9050305@bigfoot.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