Re: Block level parallel vacuum WIP

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block level parallel vacuum WIP
Date: 2016-08-23 12:25:20
Message-ID: CAGTBQpZk1bsNWgPmpY+=f0qAFUt0yNB=PibyC7zvWqh0NMpSqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 23, 2016 at 8:02 AM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> 2. Vacuum table and index (after 10000 transaction executed)
> 1 worker : 12 sec
> 2 workers : 49 sec
> 3 workers : 54 sec
> 4 workers : 53 sec
>
> As a result of my test, since multiple process could frequently try to
> acquire the cleanup lock on same index buffer, execution time of
> parallel vacuum got worse.
> And it seems to be effective for only table vacuum so far, but is not
> improved as expected (maybe disk bottleneck).

Not only that, but from your description (I haven't read the patch,
sorry), you'd be scanning the whole index multiple times (one per
worker).

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2016-08-23 12:26:31 Re: Logical decoding of sequence advances, part II
Previous Message Васильев Дмитрий 2016-08-23 12:25:14 Re: Block level parallel vacuum WIP