From: | Reydan Cankur <reydan(dot)cankur(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Best Profiler for PostgreSQL |
Date: | 2009-09-09 10:15:08 |
Message-ID: | A7816B82-0630-4424-B6B9-2CD037BFC0A8@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
I am running PostgreSQL-8.4.0 on a SMP Server which has 32 processors
(32X2=64 cores). I am working on database parallelism and I need to do
profiling in order to find the relevant parts to parallelize. I wrote
15 queries which are performing select, sort, join, and aggregate
functions and I want to profile these queries and try to understand
where postgresql spends more time and then I will try to parallelize
source code(time spending parts) by using openMP. But I need guidance
about profiling tool, which is the best tool to profile queries. I
used gprof but I want to profile with a more advanced tool. Options
are oprofile and valgrind.
1) I can not decide which best suits for query profiling. oprofile or
valgrind?
2) Also for both I can not find documentation about profiling steps.
Please help,
Reydan
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Cox | 2009-09-09 13:56:53 | Re: partitioning max() sql not using index |
Previous Message | Heikki Linnakangas | 2009-09-09 10:05:22 | Re: partitioning max() sql not using index |