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-21 02:31:37 |
Message-ID: | CA+hUKGKKhdSNPO1a5xe=HkeUpvsFCsODOib-fDDsi1+aDR+XWQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 21, 2020 at 1:38 PM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
>> >> 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)
> 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)
Thanks. So it seems like Linux, Windows and anything using ZFS are
OK, which probably explains why we hadn't heard complaints about it.
From | Date | Subject | |
---|---|---|---|
Next Message | David Gilman | 2020-05-21 03:05:01 | Re: Warn when parallel restoring a custom dump without data offsets |
Previous Message | Kyotaro Horiguchi | 2020-05-21 02:25:35 | Re: Optimizer docs typos |