Re: Parallel Seq Scan vs kernel read ahead

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel Seq Scan vs kernel read ahead
Date: 2020-05-20 23:47:47
Message-ID: CA+hUKGK=hyqyru1UKJQHiqUC_327ZW_yU-or=aNWueFN9UP3yw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 21, 2020 at 11:15 AM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
> postgres=# set max_parallel_workers_per_gather = 0;
> Time: 227238,445 ms (03:47,238)
> postgres=# set max_parallel_workers_per_gather = 1;
> Time: 138027,351 ms (02:18,027)

Ok, so it looks like NT/NTFS isn't suffering from this problem.
Thanks for testing!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2020-05-20 23:50:45 Re: Parallel Seq Scan vs kernel read ahead
Previous Message Ranier Vilela 2020-05-20 23:14:12 Re: Parallel Seq Scan vs kernel read ahead