From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Subject: | Re: cost based vacuum (parallel) |
Date: | 2019-11-04 19:08:18 |
Message-ID: | 20191104190818.kbvcris4dynrjd6u@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2019-11-04 14:06:19 -0500, Stephen Frost wrote:
> * Jeff Janes (jeff(dot)janes(at)gmail(dot)com) wrote:
> > On Mon, Nov 4, 2019 at 1:54 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> > > For parallel vacuum [1], we were discussing what is the best way to
> > > divide the cost among parallel workers but we didn't get many inputs
> > > apart from people who are very actively involved in patch development.
> > > I feel that we need some more inputs before we finalize anything, so
> > > starting a new thread.
> >
> > Maybe a I just don't have experience in the type of system that parallel
> > vacuum is needed for, but if there is any meaningful IO throttling which is
> > active, then what is the point of doing the vacuum in parallel in the first
> > place?
>
> With parallelization across indexes, you could have a situation where
> the individual indexes are on different tablespaces with independent
> i/o, therefore the parallelization ends up giving you an increase in i/o
> throughput, not just additional CPU time.
How's that related to IO throttling being active or not?
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-11-04 19:09:45 | Re: Missed check for too-many-children in bgworker spawning |
Previous Message | Stephen Frost | 2019-11-04 19:06:19 | Re: cost based vacuum (parallel) |