From: Mark Wong <markw@osdl.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: neilc@samurai.com
Cc: pgsql-performance@postgresql.org
Subject: Re: futex results with dbt-3
Date: Wed, 20 Oct 2004 15:05:28 -0700
Message-ID: <20041020150528.B7838@osdl.org> (raw)
In-Reply-To: <4176A2C1.3070205@colorfullife.com>
References: <417221B5.1050704@colorfullife.com>
<20151.1098222733@sss.pgh.pa.us>
<417697A5.1050600@colorfullife.com>
<7178.1098292535@sss.pgh.pa.us>
<4176A2C1.3070205@colorfullife.com>
On Wed, Oct 20, 2004 at 07:39:13PM +0200, Manfred Spraul wrote:
>
> But: According to the descriptions the problem is a context switch
> storm. I don't see that cache line bouncing can cause a context switch
> storm. What causes the context switch storm? If it's the pg_usleep in
> s_lock, then my patch should help a lot: with pthread_rwlock locks, this
> line doesn't exist anymore.
>
I gave Manfred's patch a try on my 4-way Xeon system with Tom's test_script.sql
files. I ran 4 processes of test_script.sql against 8.0beta3 (without any
patches) and from my observations with top, the cpu utilization between
processors was pretty erratic. They'd jump anywhere from 30% - 70%.
With the futex patches that Neil and Gavin have been working on, I'd see
the processors evenly utilized at about 50% each.
With just Manfred's patch I think there might be a problem somewhere with
the patch, or something else, as only one processor is doing anything at a
time and 100% utilized.
Here are some other details, per Manfred's request:
Linux 2.6.8.1 (on a gentoo distro)
gcc 3.3.4
glibc 2.3.3.20040420
Mark
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: markw@osdl.org, manfred@colorfullife.com, tgl@sss.pgh.pa.us, neilc@samurai.com
Subject: Re: futex results with dbt-3
In-Reply-To: <20041020150528.B7838@osdl.org>
* 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