Re: PG-Strom - A GPU optimized asynchronous executor module - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PG-Strom - A GPU optimized asynchronous executor module
Date
Msg-id CA+TgmoYskq6pA+X+O4nJYrc31qUNpyC0O1fsTVTRFzAAuwAQ+A@mail.gmail.com
Whole thread Raw
In response to PG-Strom - A GPU optimized asynchronous executor module  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Responses Re: PG-Strom - A GPU optimized asynchronous executor module  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
List pgsql-hackers
On Sun, Jan 22, 2012 at 10:48 AM, Kohei KaiGai <kaigai@kaigai.gr.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Next steps on pg_stat_statements normalisation
Next
From: Noah Misch
Date:
Subject: Re: [PATCH] Support for foreign keys with arrays