Re: Optimize kernel readahead using buffer access strategy - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Optimize kernel readahead using buffer access strategy
Date
Msg-id CAGTBQpb5CfqkTCPxQ34ZmMEEQq4hxDWCaXP59+t8AD=GOt85GQ@mail.gmail.com
Whole thread Raw
In response to Re: Optimize kernel readahead using buffer access strategy  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Responses Re: Optimize kernel readahead using buffer access strategy
List pgsql-hackers
On Tue, Dec 10, 2013 at 5:03 AM, KONDO Mitsumasa
<kondo.mitsumasa@lab.ntt.co.jp> wrote:
> I revise this patch and re-run performance test, it can work collectry in
> Linux and no complile wanings. I add GUC about enable_kernel_readahead
> option in new version. When this GUC is on(default), it works in
> POSIX_FADV_NORMAL which is general readahead in OS. And when it is off, it
> works in POSXI_FADV_RANDOM or POSIX_FADV_SEQUENTIAL which is judged by
> buffer hint in Postgres, readahead parameter is optimized by postgres. We
> can change this parameter in their transactions everywhere and everytime.

I'd change the naming to

enable_readahead=os|fadvise

with os = on, fadvise = off

And, if you want to keep the on/off values, I'd reverse them. Because
off reads more like "I don't do anything special", and in your patch
it's quite the opposite.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: tracking commit timestamps
Next
From: Greg Stark
Date:
Subject: Re: ANALYZE sampling is too good