Re: Parallel Seq Scan vs kernel read ahead

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(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-21 01:37:36
Message-ID: CAEudQAraz5Aj7hUR91z1Qmqxwu8rq_Kn+syYEL71S06AFxsyng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em qua., 20 de mai. de 2020 às 21:03, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
escreveu:

> On Thu, May 21, 2020 at 11:51 AM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
> wrote:
> > Em qua., 20 de mai. de 2020 às 20:48, Thomas Munro <
> thomas(dot)munro(at)gmail(dot)com> escreveu:
> >> 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!
> >
> > Maybe it wasn’t clear, the tests were done with your patch applied.
>
> Oh! And how do the times look without it?
>
Vanila Postgres (latest)

create table t as select generate_series(1, 800000000)::int i;
set max_parallel_workers_per_gather = 0;
Time: 210524,317 ms (03:30,524)
set max_parallel_workers_per_gather = 1;
Time: 146982,737 ms (02:26,983)

regards,
Ranier Vilela

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2020-05-21 01:40:58 Re: Subplan result caching
Previous Message Kyotaro Horiguchi 2020-05-21 01:11:26 Re: Expand the use of check_canonical_path() for more GUCs