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 02:20:44
Message-ID: CA+TgmoYskq6pA+X+O4nJYrc31qUNpyC0O1fsTVTRFzAAuwAQ+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 22, 2012 at 10:48 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> I tried to implement a fdw module that is designed to utilize GPU
> devices to execute
> qualifiers of sequential-scan on foreign tables managed by this module.
>
> It was named PG-Strom, and the following wikipage gives a brief
> overview of this module.
>    http://wiki.postgresql.org/wiki/PGStrom
>
> In our measurement, it achieves about x10 times faster on
> sequential-scan with complex-
> qualifiers, of course, it quite depends on type of workloads.

That's pretty neat. In terms of tuning the non-GPU based
implementation, have you done any profiling? Sometimes that leads to
an "oh, woops" moment.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2012-01-23 02:30:45 Re: [PATCH] Support for foreign keys with arrays
Previous Message Robert Haas 2012-01-23 02:17:09 Re: Next steps on pg_stat_statements normalisation