Re: Optimize kernel readahead using buffer access strategy

From: KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Subject: Re: Optimize kernel readahead using buffer access strategy
Date: 2013-12-12 10:57:53
Message-ID: 52A996B1.7050608@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(2013/12/12 9:30), Claudio Freire wrote:
> On Wed, Dec 11, 2013 at 3:14 AM, KONDO Mitsumasa
> <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>
>>> enable_readahead=os|fadvise
>>>
>>> with os = on, fadvise = off
>>
>> Hmm. fadvise is method and is not a purpose. So I consider another idea of
>> this GUC.
>
> Yeah, I was thinking of opening the door for readahead=aio, but
> whatever clearer than on-off would work ;)

I'm very interested in Postgres with libaio, and I'd like to see the perfomance
improvements. I'm not sure about libaio, however, it will face
exclusive-buffer-lock problem in asynchronous IO.

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2013-12-12 11:04:17 Re: Time-Delayed Standbys
Previous Message Simon Riggs 2013-12-12 10:56:36 pgsql: Allow time delayed standbys and recovery