From: Mark Wong <markw@osdl.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: josh@agliodbs.com, Simon Riggs <simon@2ndquadrant.com>
Cc: testperf-general@pgfoundry.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
Date: Fri, 15 Oct 2004 14:32:06 -0700
Message-ID: <20041015143206.A17724@osdl.org> (raw)
In-Reply-To: <26451.1097875649@sss.pgh.pa.us>
References: <NOEFLCFHBPDAFHEIPGBOGEEECGAA.simon@2ndquadrant.com>
<200410151313.13624.josh@agliodbs.com>
<26068.1097872442@sss.pgh.pa.us>
<200410151338.17277.josh@agliodbs.com>
<26451.1097875649@sss.pgh.pa.us>
On Fri, Oct 15, 2004 at 05:27:29PM -0400, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
> >> I suspect the reason recalc_sigpending_tsk is so high is that the
> >> original coding of PG_TRY involved saving and restoring the signal mask,
> >> which led to a whole lot of sigsetmask-type kernel calls. Is this test
> >> with beta3, or something older?
>
> > Beta3, *without* Gavin or Neil's Futex patch.
>
> Hmm, in that case the cost deserves some further investigation. Can we
> find out just what that routine does and where it's being called from?
>
There's a call-graph feature with oprofile as of version 0.8 with
the opstack tool, but I'm having a terrible time figuring out why the
output isn't doing the graphing part. Otherwise, I'd have that
available already...
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, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, testperf-general@pgfoundry.org
Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
In-Reply-To: <20041015143206.A17724@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