| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | John Lumby <johnlumby(at)hotmail(dot)com> |
| Cc: | pgsql hackers <pgsql-hackers(at)postgresql(dot)org>, Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Subject: | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
| Date: | 2014-05-28 21:51:50 |
| Message-ID: | CAM3SWZRby63v=rvvacjppghWhtgS8UROunw4ozSjg-DHZz9xCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 27, 2014 at 3:17 PM, John Lumby <johnlumby(at)hotmail(dot)com> wrote:
> Below I am pasting the README we have written for this new functionality
> which mentions some of the measurements, advantages (and disadvantages)
> and we welcome all and any comments on this.
I think that this is likely to be a useful area to work on, but I
wonder: can you suggest a useful test-case or benchmark to show the
advantages of the patch you posted? You mention a testcase already,
but it's a little short on details. I think it's always a good idea to
start with that when pursuing a performance feature.
Have you thought about things like specialized prefetching for nested
loop joins?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-05-28 22:32:18 | Re: SP-GiST bug. |
| Previous Message | Andres Freund | 2014-05-28 21:27:21 | Re: pgsql: Fix bogus %name-prefix option syntax in all our Bison files. |