From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mark Wong <markw(at)osdl(dot)org> |
Cc: | josh(at)agliodbs(dot)com, Simon Riggs <simon(at)2ndquadrant(dot)com>, testperf-general(at)pgfoundry(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |
Date: | 2004-10-15 21:44:34 |
Message-ID: | 26629.1097876674@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Mark Wong <markw(at)osdl(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Wong | 2004-10-15 22:10:22 | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |
Previous Message | Mark Wong | 2004-10-15 21:32:06 | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Wong | 2004-10-15 21:56:30 | Re: mmap (was First set of OSDL Shared Mem scalability results, some wierdness ... |
Previous Message | Tom Lane | 2004-10-15 21:37:50 | Re: mmap (was First set of OSDL Shared Mem scalability results, some wierdness ... |