From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "Constantin S(dot) Pan" <kvapen(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [WIP] speeding up GIN build with parallel workers |
Date: | 2016-03-18 15:18:46 |
Message-ID: | CA+TgmobApGYQiO8J=Gauq2chV2X96HjZmk2m6xwMYjWpTk9UXg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 17, 2016 at 11:42 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-03-18 15:21:00 | Re: silent data loss with ext4 / all current versions |
Previous Message | David Steele | 2016-03-18 15:16:55 | Re: 2016-03 Commitfest |