From: | Yeb Havinga <yebhavinga(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Greg Stark <stark(at)mit(dot)edu>, "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Amazon now supporting GPU focused EC2 instances |
Date: | 2010-11-15 11:58:57 |
Message-ID: | 4CE12081.7020304@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2010-11-15 12:37, Thom Brown wrote:
> On 15 November 2010 11:26, Greg Stark <stark(at)mit(dot)edu
> <mailto:stark(at)mit(dot)edu>> wrote:
>
> I keep wondering if there's a role for GPUs in Postgres and haven't
> figure out how to integrate them yet but the day when we'll be
> expected to exploit them seems to be getting nearer:
>
> http://aws.typepad.com/aws/2010/11/new-ec2-instance-type-the-cluster-gpu-instance.html
>
>
> Is this somewhere OpenCL is an option?
There is a talk about PgOpenCL upcoming -
http://www.postgresql.eu/events/schedule/pgday2010/session/56-introduction-to-pgopencl-a-new-procedural-language-for-postgresql-unlocking-the-power-of-the-gpgpu/
Maybe I've sent this link earlier, but the VLDB 2008 paper Parallelizing
Query Optimization (http://www.vldb.org/pvldb/1/1453882.pdf) might be
interesting: not much IO between CPU and GPU. (hmm how much catalog
access is necessary for cost estimization)). I suspect the biggest
challenge is rewriting essential parts into a SIMD algorithm.
regards,
Yeb Havinga
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-11-15 12:56:17 | Re: changing MyDatabaseId |
Previous Message | Greg Stark | 2010-11-15 11:49:57 | Re: Amazon now supporting GPU focused EC2 instances |