From: Luke Lonergan <llonergan@greenplum.com>
To: Kari Lavikka <tuner@bdb.fi>
To: pgsql-performance@postgresql.org
Subject: Re: Finding bottleneck
Date: Thu, 28 Jul 2005 11:27:36 -0700
Message-ID: <BF0E71A8.A2AF%llonergan@greenplum.com> (raw)
In-Reply-To: <Pine.HPX.4.62.0507281215420.2164@purple.bdb.fi>
On 7/28/05 2:21 AM, "Kari Lavikka" <tuner@bdb.fi> wrote:
There's a new profiling tool called oprofile:
http://oprofile.sourceforge.net/download/
that can be run without instrumenting the binaries beforehand. To actually
find out what the code is doing during these stalls, oprofile can show you
in which routines the CPU is spending time when you start/stop the
profiling.
As an alternative to the "guess->change parameters->repeat" approach, this
is the most direct way to find the exact nature of the problem.
- Luke
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: llonergan@greenplum.com, tuner@bdb.fi
Subject: Re: Finding bottleneck
In-Reply-To: <BF0E71A8.A2AF%llonergan@greenplum.com>
* 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