Re: Profiling PostgreSQL
От
David Boreham
Тема
Re: Profiling PostgreSQL
Дата
Msg-id
537DFCEC.40800@boreham.org
Ответ на
Profiling PostgreSQL (Dimitris Karampinas)
Список
Дерево обсуждения
Profiling PostgreSQL Dimitris Karampinas <dkarampin@gmail.com>
Re: Profiling PostgreSQL Tom Lane <tgl@sss.pgh.pa.us>
Re: Profiling PostgreSQL Michael Paquier <michael.paquier@gmail.com>
Re: Profiling PostgreSQL Dimitris Karampinas <dkarampin@gmail.com>
Re: Profiling PostgreSQL Pavel Stehule <pavel.stehule@gmail.com>
Re: Profiling PostgreSQL Jeff Janes <jeff.janes@gmail.com>
Re: Profiling PostgreSQL Dimitris Karampinas <dkarampin@gmail.com>
Re: Profiling PostgreSQL Jeff Janes <jeff.janes@gmail.com>
Re: Profiling PostgreSQL Dimitris Karampinas <dkarampin@gmail.com>
Re: Profiling PostgreSQL Matheus de Oliveira <matioli.matheus@gmail.com>
Re: Profiling PostgreSQL David Boreham <david_list@boreham.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.
В списке pgsql-performance по дате отправления
