From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
---|---|
To: | Alexander Staubo <alex(at)purefiction(dot)net> |
Cc: | "Billings, John" <John(dot)Billings(at)paetec(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Using the GPU |
Date: | 2007-06-11 08:31:42 |
Message-ID: | 466D086E.3040107@magproductions.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alexander Staubo wrote:
> On 6/8/07, Billings, John <John(dot)Billings(at)paetec(dot)com> wrote:
>> If so which part of the database, and what kind of parallel
>> algorithms would be used?
>
> GPUs are parallel vector processing pipelines, which as far as I can
> tell do not lend themselves right away to the data structures that
> PostgreSQL uses; they're optimized for processing high volumes of
> homogenously typed values in sequence.
But wouldn't vector calculations on database data be sped up? I'm
thinking of GIS data, joins across ranges like matching one (start, end)
range with another, etc.
I realize these are rather specific calculations, but if they're
important to your application...
OTOH modern PC GPU's are optimized for pushing textures; basically
transferring a lot of data in as short a time as possible. Maybe it'd be
possible to move result sets around that way? Do joins even maybe?
And then there are the vertex and pixel shaders...
It'd be kind of odd though, to order a big time database server with a
high-end gaming card in it :P
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2007-06-11 09:01:36 | Re: Postmaster processes taking all the CPU |
Previous Message | Simon Riggs | 2007-06-11 08:30:48 | Re: Suppress checking of chmod 700 on data-dir? |