From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parallel query execution |
Date: | 2013-01-24 23:17:18 |
Message-ID: | 20130124231718.GI21914@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 24, 2013 at 02:34:49PM -0800, Paul Ramsey wrote:
> On Tuesday, January 15, 2013 at 2:14 PM, Bruce Momjian wrote:
>
> I mentioned last year that I wanted to start working on parallelism:
>
> https://wiki.postgresql.org/wiki/Parallel_Query_Execution
>
> I believe it is time to start adding parallel execution to the backend.
> We already have some parallelism in the backend:
> effective_io_concurrency and helper processes. I think it is time we
> start to consider additional options
>
> Parallelism isn't going to help all queries, in fact it might be just a
> small subset, but it will be the larger queries. The pg_upgrade
> parallelism only helps clusters with multiple databases or tablespaces,
> but the improvements are significant.
>
>
> I just got out of a meeting that included Oracle Spatial folks, who
> were boasting of big performance increases in enabling parallel query
> on their spatial queries. Basically the workloads on things like big
> spatial joins are entirely CPU bound, so they are seeing that adding
> 15 processors makes things 15x faster. Spatial folks would love love
> love to see parallel query execution.
I added PostGIS under the "Expensive Functions" opportunity:
https://wiki.postgresql.org/wiki/Parallel_Query_Execution#Specific_Opportunities
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-01-24 23:21:34 | Re: Performance patch for Win32 |
Previous Message | Bruce Momjian | 2013-01-24 23:15:33 | Re: COPY FREEZE has no warning |