Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 37EA92E2E62 for ; Sat, 1 Dec 2007 12:39:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 98591-04 for ; Sat, 1 Dec 2007 12:39:16 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by postgresql.org (Postfix) with ESMTP id 90C212E004D for ; Sat, 1 Dec 2007 12:39:16 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so3967075waf for ; Sat, 01 Dec 2007 08:39:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=YElpZPdhBUoz4b2et+uQaQL9XG4QmNDVZclRFEGh0BI=; b=FF5c8F8Fn87VLAo0tUCQB8AfYlDeBxSjkmO2wgI/MZ6VX4EHQgoao7F6Lei6svIgMEzoRY18TtX8aNSGRFcP4Md49Kk6AAT0CpAvVkWXFs07ikLxSHjVXMxOf9863jULKipxBNuKF7oZuncVyFYWhO3YLdIIgqzljeRP/zIY86o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZzIO/VrSCDFBtU8t8t10ItBlKtmCE2WSWzd6Q5+eE03bIiC68npC4vLy81k+CgfxaIpWFUd5WSeVeo8r9hfG1bDNgYR+SCMPXNQW/xCBx74ILWAUZrv0eJdUF9zJhTVQZWwdDgRB1eu6Wa7WL+lNOqx+/ie+eFa2LDj94ImdqBg= Received: by 10.142.231.7 with SMTP id d7mr923258wfh.1196527155395; Sat, 01 Dec 2007 08:39:15 -0800 (PST) Received: by 10.143.19.7 with HTTP; Sat, 1 Dec 2007 08:39:15 -0800 (PST) Message-ID: <36e682920712010839k4cf3b778h518aea2c5e3eb9bc@mail.gmail.com> Date: Sat, 1 Dec 2007 11:39:15 -0500 From: "Jonah H. Harris" To: "henk de wit" Subject: Re: Utilizing multiple cores for one query Cc: "pgsql-performance@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <36e682920712010531k47871797ge19ceaddad9a7ff6@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/4 X-Sequence-Number: 27820 On Dec 1, 2007 9:42 AM, henk de wit wrote: > Wouldn't this offer some opportunities for running things on multiple cores? No, it's not actually parallel in the same sense. > Yes, I noticed this project before. At the time it was not really clear how > stable and/or how well supported this is. It indeed seems to support > parallel queries automatically by being able to rewrite standard queries. It > does seem it needs different DB nodes and is thus probably not able to use > multiple cores of a single DBMS. I've seen it actually set up to use multiple connections to the same DBMS. How well it would work is pretty much dependent on your application and the amount of parallelization you could actually gain. > Also, I could not really find how well > pgpool-II is doing at making judgments of the level of parallelization it's > going to use. E.g. when there are 16 nodes in the system with a currently > low utilization, a single query may be split into 16 pieces. On the other > hand, when 8 of these nodes are heavily utilized, splitting to 8 pieces > might be better. etc. IIRC, it doesn't plan parallelization that way. It looks at what is partitioned (by default) on different nodes and parallelizes based on that. As I said earlier, you can partition a single node and put pgpool-II on top of it to gain some parallelization. Unfortunately, it isn't capable of handling things like parallel index builds or other useful maintenance features... but it can do fairly good query result parallelization. -- Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com Edison, NJ 08837 | http://www.enterprisedb.com/