Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore
Date: 2015-12-01 00:31:15
Message-ID: CAM3SWZSD4mUDc4HQLJ2bNTOkYs0Q+UP-RY9D439VGLCMbVOqzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 30, 2015 at 1:04 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> For example, the 50 million tuple test has over 8% of its runtime
> shaved off. This seems to be a consistent pattern.

I included the nitty-gritty details of this case in something attached
to a mail I just sent, over in the "Quicksort for every external sort
run" thread, FWIW.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2015-12-01 01:12:13 Re: Using quicksort for every external sort run
Previous Message Peter Geoghegan 2015-12-01 00:29:38 Re: Using quicksort for every external sort run