Re: [WIP] speeding up GIN build with parallel workers - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [WIP] speeding up GIN build with parallel workers
Date
Msg-id CA+TgmobApGYQiO8J=Gauq2chV2X96HjZmk2m6xwMYjWpTk9UXg@mail.gmail.com
Whole thread Raw
In response to Re: [WIP] speeding up GIN build with parallel workers  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Thu, Mar 17, 2016 at 11:42 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> I think here the comparison should be between the case of (active backend +
> 1 worker) with (passive backend + 1 worker) or  (active backend + 2 worker)
> with (passive backend + 2 workers).  I don't think it is good assumption
> that workers are always freely available and you can use them as and when
> required for any operation.

Strong +1.  The pool of background workers is necessarily quite
limited and you can't just gobble them up.  I'm not saying that it's
absolutely essential that the leader can also participate, but saying
that 1 active leader + 1 worker is only 2% faster than 1 passive
leader + 2 workers is not comparing apples to apples.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: 2016-03 Commitfest
Next
From: Robert Haas
Date:
Subject: Re: silent data loss with ext4 / all current versions