Re: PG-Strom - A GPU optimized asynchronous executor module

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG-Strom - A GPU optimized asynchronous executor module
Date: 2012-01-23 13:09:11
Message-ID: CA+Tgmob6C2UiDy3eGdAdxKH0qZxju5zx7Fe-zGOgoS3svrpBEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 23, 2012 at 1:38 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> What options are available to see rate of workloads of components
> within a particular query?

I usually use oprofile, though I'm given to understand it's been
superseded by a new tool called perf. I haven't had a chance to
experiment with perf yet, though.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-01-23 13:11:04 Re: Online base backup from the hot-standby
Previous Message Robert Haas 2012-01-23 13:06:46 Re: Removing freelist (was Re: Should I implement DROP INDEX CONCURRENTLY?)