From: Stephen Frost <sfrost@snowman.net>
To: Karel K. Rozhoň <karel.rozhon@gmail.com>
Cc: pgsql-students@postgresql.org
Subject: Re: Google Summer of code 2013
Date: Mon, 15 Apr 2013 12:27:45 -0400
Message-ID: <20130415162745.GT4361@tamriel.snowman.net> (raw)
In-Reply-To: <20130415175122.ca9c29b83ccd4d5f4cd490f6@gmail.com>
References: <20130413183912.e74dfcdc8f0072e2b6c2fb24@gmail.com>
<20130414221640.GQ4361@tamriel.snowman.net>
<516B59D9.5070106@fuzzy.cz>
<20130415015400.GR4361@tamriel.snowman.net>
<20130415175122.ca9c29b83ccd4d5f4cd490f6@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-students>
* Karel K. Rozhoň (karel.rozhon@gmail.com) wrote:
> Of course I don't see all aspects of this problem, so I cannot tell what should be good for future. But I have done some profiles of group by select and I believe, parallel calling of some hash procedures could help.
There seems to be some confuison here. It's certainly true that *many*
(most? all?) pieces of query processing would benefit from parallel
execution; there is no debate on that.
The issue is that PG is not currently set up to do *any* per-query
parallel processing and it is *not* a trival thing to change that. We
can talk all day about how wonderful it'd be to do parallel hashing,
parallel sorting, etc, but until PG has a way to parallelize query
processing, there's really no point to writing code to parallelize
individual nodes.
> Of course I know, these simply case is only teoretical and in real tables are data much more complicated, but as I can see, almost 40% of CPU time was computed only one hash function: hash_search_with_hash_value.
Improvements to that would be great, but you can't simply call
pthread_create() in a PG backend and expect things to work.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 197B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-students@postgresql.org
Cc: sfrost@snowman.net, karel.rozhon@gmail.com
Subject: Re: Google Summer of code 2013
In-Reply-To: <20130415162745.GT4361@tamriel.snowman.net>
References: <20130413183912.e74dfcdc8f0072e2b6c2fb24@gmail.com> <20130414221640.GQ4361@tamriel.snowman.net> <516B59D9.5070106@fuzzy.cz> <20130415015400.GR4361@tamriel.snowman.net> <20130415175122.ca9c29b83ccd4d5f4cd490f6@gmail.com> <20130415162745.GT4361@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox