Re: Extended Prefetching using Asynchronous IO - proposal and patch - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Extended Prefetching using Asynchronous IO - proposal and patch
Date
Msg-id CAGTBQpY0jCuMgXudn5_e=9o3OHezk3vzx_VhmSEnpUYiwOvsZg@mail.gmail.com
Whole thread Raw
In response to Re: Extended Prefetching using Asynchronous IO - proposal and patch  (johnlumby <johnlumby@hotmail.com>)
List pgsql-hackers
On Sat, May 31, 2014 at 9:44 PM, johnlumby <johnlumby@hotmail.com> wrote:
> I'll try to do some measuring of performance with:
> a) git head
> b) git head + patch as-is
> c) git head + patch without aio_suspend in foreign processes (just re-read)
> d) git head + patch with a lwlock (or whatever works) instead of aio_suspend
>
> a-c will be the fastest, d might take some while.
>
> I'll let you know of the results as I get them.
>
>
> Claudio,  I am not quite sure if what I am submitting now is
> quite the same as any of yours.       As I promised before,  but have
> not yet done,  I will package one or two of my benchmarks and
> send them in.


It's a tad different. c will not do polling on the foreign process, I
will just let PG do the read again. d will be like polling, but
without the associated CPU overhead.



pgsql-hackers by date:

Previous
From: johnlumby
Date:
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch
Next
From: Jim Nasby
Date:
Subject: Re: Changeset Extraction v7.6.1