PgPool parallel query performance rules of thumb

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Pgsql-Performance <pgsql-performance@xxxxxxxxxxxxxx>
Subject: PgPool parallel query performance rules of thumb
From: John Beaver <john.e.beaver@xxxxxxxxx>
Date: Wed, 04 Jun 2008 11:58:32 -0400
In-reply-to: <4846B244.7020307@xxxxxxxxxxxxx>
References: <4846AA49.5010601@xxxxxxxxxxxxx> <24864.1212592208@xxxxxxxxxxxxx> <4846B244.7020307@xxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.14 (Macintosh/20080421)

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 querymode. Under what circumstances could I expect the most benefit fromquery parallelization as implemented by PgPool?

Follow-Ups:
- Re: PgPool parallel query performance rules of thumb
  - From: Mason Sharp

References:
- backend pid changing
  - From: Lewis Kapell
- Re: backend pid changing
  - From: Tom Lane
- Re: backend pid changing
  - From: Lewis Kapell

Prev by Date: Re: backend pid changing
Next by Date: Re: insert/update tps slow with indices on table > 1M rows
Previous by thread: Re: backend pid changing
Next by thread: Re: PgPool parallel query performance rules of thumb
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux