Re: Parallel Seq Scan vs kernel read ahead
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Ranier Vilela <ranier.vf@gmail.com>,
Amit Kapila <amit.kapila16@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-06-10T05:39:26Z
Lists: pgsql-hackers
On Wed, 10 Jun 2020 at 17:21, Thomas Munro <thomas.munro@gmail.com> wrote: > I also heard from Andres that he likes this patch with his AIO > prototype, because of the way request merging works. So it seems like > there are several reasons to want it. > > But ... where should we get the maximum step size from? A GUC? I guess we'd need to determine if other step sizes were better under any conditions. I guess one condition would be if there was a LIMIT clause. I could check if setting it to 1024 makes any difference, but I'm thinking it won't since I got fairly consistent results on all worker settings with the patched version. David
Commits
-
Allocate consecutive blocks during parallel seqscans
- 56788d2156fc 14.0 landed