Re: Parallel Seq Scan vs kernel read ahead - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Parallel Seq Scan vs kernel read ahead
Date
Msg-id CAA4eK1+0M9WP-v3S=WsCnkazmGSZseBGU-HzNph88Atepx+0zg@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Seq Scan vs kernel read ahead  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Parallel Seq Scan vs kernel read ahead
List pgsql-hackers
On Wed, Jul 22, 2020 at 5:25 AM David Rowley <dgrowleyml@gmail.com> wrote:
>
> I understand that Amit wrote:
>
> On Fri, 17 Jul 2020 at 21:18, Amit Kapila <amit.kapila16@gmail.com> wrote:
> > I think recreating the database and restarting the server after each
> > run might help in getting consistent results.  Also, you might want to
> > take median of three runs.
>
> Please also remember, if you're recreating the database after having
> restarted the machine that creating the table will likely end up
> caching some of the pages either in shared buffers or the Kernel's
> cache.
>

Yeah, that is true but every time before the test the same amount of
data should be present in shared buffers (or OS cache) if any which
will help in getting consistent results.  However, it is fine to
reboot the machine as well if that is a convenient way.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions
Next
From: Thomas Munro
Date:
Subject: Re: Parallel Seq Scan vs kernel read ahead