Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 9628D2E006E for ; Wed, 4 Jun 2008 12:58:54 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 91422-08 for ; Wed, 4 Jun 2008 12:58:45 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.190]) by developer.postgresql.org (Postfix) with ESMTP id D82E62E0062 for ; Wed, 4 Jun 2008 12:58:44 -0300 (ADT) Received: by rn-out-0910.google.com with SMTP id k40so86595rnd.0 for ; Wed, 04 Jun 2008 08:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=M1wKzsnW+MvpS7kFd8zNBBBd55/2K2cWVOY2Jj7+A3U=; b=asie61MDG/hIkC4LGxDGU0firT3jk6k5wPge5EIRGIVAiMCJ7/Ium9Krkp+FmcqFNW nWWf7voK9wqZ8KFYQqFitqQW3ecTov5C1ZLCyS+IQBptYJabj/RDYFLJfMM69D2pgpmn 56T84HlgQQ2dqdK8PQkkchiCZE4e96z7131Bo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=lmzHy4N57genk1ZrqPzGx1+VYXiZ2+cIA079d/P0LlIxFW0djpOrVoFi6teVorhXpl gY5XuhPgZfWOuwuBkIEV7FSJPk2U45rSD243xDakiPF7VNaRkHAV/N5cr6EhsIzq1GF9 BmRDF0eKteVAIfJdrh8npLy7E+xNzrwdugjzk= Received: by 10.114.159.5 with SMTP id h5mr84649wae.222.1212595115195; Wed, 04 Jun 2008 08:58:35 -0700 (PDT) Received: from dhc012690.med.harvard.edu ( [134.174.169.21]) by mx.google.com with ESMTPS id i40sm5136392wxd.29.2008.06.04.08.58.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 04 Jun 2008 08:58:34 -0700 (PDT) Message-ID: <4846BBA8.4090501@gmail.com> Date: Wed, 04 Jun 2008 11:58:32 -0400 From: John Beaver User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Pgsql-Performance Subject: PgPool parallel query performance rules of thumb References: <4846AA49.5010601@setonhome.org> <24864.1212592208@sss.pgh.pa.us> <4846B244.7020307@setonhome.org> In-Reply-To: <4846B244.7020307@setonhome.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200806/25 X-Sequence-Number: 30375 Hi, I'm trying to make use of a cluster of 40 nodes that my group has, and I'm curious if anyone has experience with PgPool's parallel query mode. Under what circumstances could I expect the most benefit from query parallelization as implemented by PgPool?