Message-ID: <537DFCEC.40800@boreham.org>
Date: Thu, 22 May 2014 07:34:36 -0600
From: David Boreham <david_list@boreham.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Profiling PostgreSQL
References: 
 <CAC_Q3NwxzpZ41iByo8PKvROT4BbZRedCuJZGBVFsg-iGvCivFg@mail.gmail.com>
In-Reply-To: 
 <CAC_Q3NwxzpZ41iByo8PKvROT4BbZRedCuJZGBVFsg-iGvCivFg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 5/22/2014 7:27 AM, Dimitris Karampinas wrote:
> Is there any way to get the call stack of a function when profiling 
> PostgreSQL with perf ?
> I configured with --enable-debug, I run a benchmark against the system 
> and I'm able to identify a bottleneck.
> 40% of the time is spent on an spinlock yet I cannot find out the 
> codepath that gets me there.
> Using --call-graph with perf record didn't seem to help.
>
> Any ideas ?
>
Can you arrange to run 'pstack' a few times on the target process 
(either manually or with a shell script)?
If the probability of the process being in the spinning state is high, 
then this approach should snag you at least one call stack.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance