Re: Optimize kernel readahead using buffer access strategy
От | Claudio Freire |
---|---|
Тема | Re: Optimize kernel readahead using buffer access strategy |
Дата | |
Msg-id | CAGTBQpb5CfqkTCPxQ34ZmMEEQq4hxDWCaXP59+t8AD=GOt85GQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Optimize kernel readahead using buffer access strategy (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>) |
Ответы |
Re: Optimize kernel readahead using buffer access strategy
|
Список | 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 по дате отправления: