From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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: Tue, 19 Oct 2004 17:52:13 -0400
Message-ID: <20151.1098222733@sss.pgh.pa.us> (raw)
In-Reply-To: <417221B5.1050704@colorfullife.com>
References: <417221B5.1050704@colorfullife.com>
Manfred Spraul <manfred@colorfullife.com> writes:
> Has anyone tried to replace the whole lwlock implementation with
> pthread_rwlock? At least for Linux with recent glibcs, pthread_rwlock is
> implemented with futexes, i.e. we would get a fast lock handling without
> os specific hacks.
"At least for Linux" does not strike me as equivalent to "without
OS-specific hacks".
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.
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, manfred@colorfullife.com, neilc@samurai.com, markw@osdl.org
Subject: Re: futex results with dbt-3
In-Reply-To: <20151.1098222733@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