From: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | james(at)mansionfamily(dot)plus(dot)com |
Cc: | Jim Nasby <jim(at)nasby(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parallel Sort |
Date: | 2013-05-24 20:03:24 |
Message-ID: | CADyhKSVT53D0sNw94FQ46N=HDKZW6b0HaHM=HNLU2u6mXQEb2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Let me introduce one thing we discussed in the developer meeting at
Ottawa. We got a consensus that pluggable exec-node may be useful to
replace a part of exec-node tree with an alternative one being
implemented by extensions; which will allow to run something like
"GpuSort" instead of existing Sort.
http://wiki.postgresql.org/wiki/PgCon_2013_Developer_Meeting#Pluggable_plan.2Fexec_nodes
2013/5/24 james <james(at)mansionfamily(dot)plus(dot)com>:
>> Have you considered GPU-based sorting? I know there's been discussion in
>> the past.
>
> If you use OpenCL, then you can use a CPU driver if there is no GPU, and
> that can allow you to leverage all the CPU cores without having to do the
> multi-thread stuff in the backend.
>
> While the compilation of a specific kernel can be quite expensive, it also
> has the effect of a JIT compiler in terms of system independence.
>
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-05-24 21:16:23 | Re: visibilitymap_set and checksums |
Previous Message | Andres Freund | 2013-05-24 20:03:05 | Re: getting rid of freezing |