Re: O_DIRECT use - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: O_DIRECT use
Date
Msg-id 200201042148.g04Lmo628419@candle.pha.pa.us
Whole thread Raw
In response to O_DIRECT use  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: O_DIRECT use  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Why exactly would we wish to minimize OS caching?
> 
> > Not sure. Someone on IRC brought it up.  If we are sequential scanning a
> > large table, caching may be bad because we are pushing out stuff already
> > in the cache that may be useful.
> 
> Yeah, but people normally try to set things up to avoid doing large
> sequential scans, at least in all the contexts where they need high
> performance.  For index searches you definitely want all the caching
> you can get.
> 
> For that matter, I would expect that O_DIRECT also defeats readahead,
> so I'd fully expect it to be a loser for seqscans too.

I am told on FreeBSD it does not disable read-ahead, just caching;
something that needs more research.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: O_DIRECT use
Next
From: Tom Lane
Date:
Subject: Re: O_DIRECT use