pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Wong <markw@osdl.org>
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 17:44:34 -0400
Message-ID: <26629.1097876674@sss.pgh.pa.us> (raw)
In-Reply-To: <20041015143206.A17724@osdl.org>
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>
	<20041015143206.A17724@osdl.org>

Mark Wong <markw@osdl.org> writes:
> On Fri, Oct 15, 2004 at 05:27:29PM -0400, Tom Lane wrote:
>> 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...

I was wondering if this might be associated with do_sigaction.
do_sigaction is only 0.23 percent of the runtime according to the
oprofile results:
http://khack.osdl.org/stp/298124/oprofile/DBT_2_Profile-all.oprofile.txt
but the profile results for the same run:
http://khack.osdl.org/stp/298124/profile/DBT_2_Profile-tick.sort
show do_sigaction very high and recalc_sigpending_tsk nowhere at all.
Something funny there.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <26629.1097876674@sss.pgh.pa.us>
Permalink:  ../26629.1097876674@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26629.1097876674@sss.pgh.pa.us

 · 

reply

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, markw@osdl.org, simon@2ndquadrant.com, testperf-general@pgfoundry.org
  Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
  In-Reply-To: <26629.1097876674@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