Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1URmG4-0005hW-N5 for pgsql-students@arkaria.postgresql.org; Mon, 15 Apr 2013 16:27:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1URmG3-0003Oj-Ty for pgsql-students@arkaria.postgresql.org; Mon, 15 Apr 2013 16:27:55 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1URmG2-0003Nk-Ro for pgsql-students@postgresql.org; Mon, 15 Apr 2013 16:27:55 +0000 Received: from cl-262.qas-01.us.sixxs.net ([2001:4830:1600:105::2] helo=tamriel.snowman.net) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1URmFw-0005xj-OK for pgsql-students@postgresql.org; Mon, 15 Apr 2013 16:27:54 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id E591A22260; Mon, 15 Apr 2013 12:27:45 -0400 (EDT) Date: Mon, 15 Apr 2013 12:27:45 -0400 From: Stephen Frost To: Karel =?utf-8?Q?K=2E_Rozho=C5=88?= Cc: pgsql-students@postgresql.org Subject: Re: Google Summer of code 2013 Message-ID: <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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vjo/qE8ere+0cLOA" Content-Disposition: inline In-Reply-To: <20130415175122.ca9c29b83ccd4d5f4cd490f6@gmail.com> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/3.2.0-4-amd64 (x86_64) X-Uptime: 12:21:50 up 172 days, 14:45, 10 users, load average: 0.13, 0.15, 0.16 User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-students Precedence: bulk Sender: pgsql-students-owner@postgresql.org --vjo/qE8ere+0cLOA Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Karel K. Rozho=C5=88 (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.=20 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 w= as computed only one hash function: hash_search_with_hash_value.=20 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 --vjo/qE8ere+0cLOA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlFsKoEACgkQrzgMPqB3kijo8QCfSLHbovGDMXNww3+oGZM8HAi3 0xQAoIZyLQRVMEapohCXp9MRBDmtVbg2 =6G2n -----END PGP SIGNATURE----- --vjo/qE8ere+0cLOA--